Editing others tickets
In Lighthouse we used to be able to edit each others tickets, so if user 'A' created a ticket user 'B' would be able to edit the ticket details. We now no longer seem to be able to do that. What do I need to do to be able to do this? I can't seem to find any permissions for it.
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Julien on 23 Jul, 2014 02:02 PM
Hi,
The old behavior led to a number of accountability problems, and we ended up removing it. Only account members/administrators can edit tickets of other users now, not regular project members.
Hope that answers your question.
Let me know if there is anything else I can do for you.
Cheers.
2 Posted by William Wragg on 23 Jul, 2014 02:10 PM
I see your point, we quite liked that feature though, it helped with collaborative ticket creation. Would it be possible to add a permission to allow it, rather than having to make everyone an admin?
3 Posted by Julien on 23 Jul, 2014 02:12 PM
Unfortunately no. We would like to keep the permissions system simple. Can you detail your use case a bit? Ie when do you find yourself wanting to edit other users' tickets?
Thanks.
4 Posted by William Wragg on 23 Jul, 2014 02:20 PM
Ah OK. Well one of the team will set-up the ticket, and as the ticket is worked on, others who are dealing with it will add details to the ticket rather than through the comments, where important updates can be lost, or get muddled in with to many none important comments.
5 Posted by Julien on 23 Jul, 2014 02:24 PM
Are you dealing with people external to your team (clients, customers)? Or are you just one team?
6 Posted by William Wragg on 23 Jul, 2014 03:02 PM
We're just one team, but with different roles, backend, UI, UX, fronted, mobile etc... and the stories are vertical, so cut across the roles, so different tasks within the story can be taken up by different people.
7 Posted by Julien on 23 Jul, 2014 04:13 PM
Is there any reason why you wouldn't put all the users as account members? Usually, that's what small teams do.
8 Posted by William Wragg on 24 Jul, 2014 06:31 AM
That's what I've done, but making everyone an administrator who can make or delete anything, just so that we can all edit a ticket seems overkill. Some people can be a little careless with administrator privileges.
9 Posted by Julien on 24 Jul, 2014 02:24 PM
I understand. Unfortunately, we removed edit privileges for mostly the same reasons: people being careless, editing things they had no business editing. So we settled on: you either trust people on your team, or you don't. If you trust them, there really shouldn't be a problem making them account members, and if you don't, well they should have the least amount of power necessary to do their job.
I know it's somewhat imperfect, and that there are always exceptions and good use cases on each side, but eventually we have to choose one path, and we didn't want to bloat Lighthouse with a complex model for rights.
I'm glad you found something that works for your team, and thanks for bearing with me and having this conversation.
Cheers!
brandi closed this discussion on 30 Jul, 2014 04:39 PM.