Oups: there is a flaw in this approach! You can only get different commands for Anonymous and Login Users. You cannot select different command for Admin users: they will just have the "Config" command automatically.
You could allow anonymous users to make new entries and restrict login to administrators. But that is certainly not what you want, so forget my suggestion altogether.
| Andreas Luedeke wrote: |
|
Hi Terry,
if you really want to do it, you can find a way to make it work. But it is not straight forward and not what ELOG is made for. Here some ideas how it could work:
- ELOG allows you to have different commands for different users. You could allow "New" and "Edit" for normal users, but "Reply" only for administrators.
- You can use "
Subst on reply <attribute> = <string>" to set a specifc fields only on reply.
- You would hide "status" & "assignee" for new entries or edit
(Show Attributes Edit = <list>), and show a "set status" field instead.
- The line "
Subst on reply status = $set status" would take care, that only an administrator can set "status" with a reply to the original entry (+ a "set assignee" field, etc.). While normal users could set "set status", it would not change the "status" field. You could provide a comment or tooltip to explain that.
- The list view or single entry view should not show the "set status", but only the "status" attribute (
List display = <list>, Show Attributes = <list>).
- Use "
Propagate attribute = status, assignee" to take care, that the original entry gets their fields set accordingly.
This is how you could do what you want. But bugzilla can do a lot more if you are looking for a bug tracking software.
Cheers, Andreas
| Terry L wrote: |
|
Hi Eddy,
Thank you for your response. I had a feeling that was the case, but I had high hopes! :) The reason I would like this feature is because I am trying to use ELOG as a software anomaly tracking log, where any user can create an ELOG and fill out "category", "computer" etc, but only administrators can fill out the "status" & "assignee". If I am lucky, this will be an added feature in a future revision.
Thanks again,
-Terry
| Edmund Hertle wrote: |
|
Hey Terry,
I don't think this is possible, since in general you cannot define config settings in a way that it would only affect specific users. For example, you also cannot have different themes for different users (as stated here: https://midas.psi.ch/elogs/Forum/68112 )
Cheers
eddy
| Terry L wrote: |
|
Good Morning,
I would like to limit the ability to edit certain attributes in an ELOG logbook, depending on the user who is logged in. I.e. if "guest" or a standard "login user" is logged in, I only want to allow the user to edit "attribute1" & "attribute2" of say, 5 attributes. However, if an Admin user or specific user, say "Terry" or "Bob" is logged in, I want to allow ALL 5 attributes to be editable. To expand on this, I may want to even limit the visibility of the attributes as well.
I've read though "Condition Attributes" section of the help page, but it is not clear to me how/if I can do this? Is that section even relevant to what I want to accomplish?
Can anyone provide some guidance?
Thank you for your time & help!
Sincerely,
Terry
|
|
|
|
|