| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2153
|
Fri Mar 2 16:39:22 2007 |
 | Justin Ellison | justin@techadvise.com | Question | | 2.6.4-179 | Hiding attributes in Detail view? | First off, thanks so much for this product. It works excellent for us as a server activity log. I have a question, which depending on the answer, might be a feature request 
As I mentioned, we use elog as a serverlog. Sometimes, but not always, we will have a Bugzilla bug # that is associated with the log entry. We then take that bug #, and build a link to our bugzilla server displaying the bug. Here's the relevant config entries:
Attributes = Author, Classification, Subject, Bug Number, Environment, Server, Bugzilla
...
#Make the list table narrow enough to fit in the browser
List display = ID, Date, Author, Subject, Server, Bugzilla
...
#We take in a Bug Number from the user, then calculate a Bugzilla link from that
Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
List Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
Hidden Attributes = Bugzilla
So, on new entry, the user has the option to enter a Bug Number. Bugzilla is not displayed because it is derived. In list view, Bug Number is not displayed, but Bugzilla is, providing a handy link to the bug on a different server.
The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes. This isn't a huge deal, it's just showing redundant data.
Is there a way to hide Bug Number on the view page? |
|
2160
|
Fri Mar 9 22:14:57 2007 |
 | Justin Ellison | justin@techadvise.com | Question | | 2.6.4-179 | Re: Hiding attributes in Detail view? | | Any takers? |
|
2161
|
Mon Mar 12 20:35:17 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.4-179 | Re: Hiding attributes in Detail view? |
| Justin Ellison wrote: | The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes. This isn't a huge deal, it's just showing redundant data.
Is there a way to hide Bug Number on the view page? |
In revision 1809 I implemented the options
Show attributes = ...
Show attributed edit = ...
The first one is for the log entry page, the second for the entry form. This way you can distinguish between the bug number and the link. The old option Hidden attributes has been dropped, since it has the same effect now as Show attributes edit. |
|
2162
|
Tue Mar 13 17:27:49 2007 |
 | Justin Ellison | justin@techadvise.com | Request | | Current | Addition of a "Restrict edit attribute" option? | It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
Sound plausible?
Justin |
|
2163
|
Tue Mar 13 20:58:07 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
| Justin Ellison wrote: | It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
|
Conditional attributes? Like:
Attributes = ..., Status
Options Status = Open{1}, Closed{2}
{2}Locked attributes = Status
Unfortunately once it's locked, the admin has to change the config file to unlock it. |
|
2167
|
Wed Mar 14 15:03:41 2007 |
| Justin Ellison | justin@techadvise.com | Request | | Current | Re: Addition of a "Restrict edit attribute" option? | Sorry, I didn't explain it enough.
This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to.
That make more sense?
Justin |
|
2168
|
Wed Mar 14 15:06:27 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
| Justin Ellison wrote: | Sorry, I didn't explain it enough.
This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to. |
I understand what you want. The conditional attributes I showed you give you that functionality, except that unlocking is a bit painful for the admin (has to edit the config file each time). Sorry, but that's all I can give you. |
|
2169
|
Wed Mar 14 15:43:51 2007 |
| Justin Ellison | justin@techadvise.com | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
| Stefan Ritt wrote: |
I understand what you want. The conditional attributes I showed you give you that functionality, except that unlocking is a bit painful for the admin (has to edit the config file each time). Sorry, but that's all I can give you. |
Now I understand what you were getting at. Sorry for the confusion. That should work fine for us - unlocking is something that shouldn't ever happen.
Thanks for the quick response!
Justin |
|