tag:help.lighthouseapp.com,2008-09-20:/discussions/problems/60881-editing-others-ticketsLighthouse: Discussion 2014-07-30T16:39:44Ztag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-23T14:02:18Z2014-07-23T14:02:18ZEditing others tickets<div><p>Hi,</p>
<p>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.</p>
<p>Hope that answers your question.</p>
<p>Let me know if there is anything else I can do for you.</p>
<p>Cheers.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-23T14:10:24Z2014-07-23T14:10:24ZEditing others tickets<div><p>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?</p></div>William Wraggtag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-23T14:12:23Z2014-07-23T14:12:23ZEditing others tickets<div><p>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?</p>
<p>Thanks.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-23T14:20:14Z2014-07-23T14:20:14ZEditing others tickets<div><p>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.</p></div>William Wraggtag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-23T14:24:42Z2014-07-23T14:24:42ZEditing others tickets<div><p>Are you dealing with people external to your team (clients,
customers)? Or are you just one team?</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-23T15:02:56Z2014-07-23T15:02:56ZEditing others tickets<div><p>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.</p></div>William Wraggtag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-23T16:13:37Z2014-07-23T16:13:37ZEditing others tickets<div><p>Is there any reason why you wouldn't put all the users as
account members? Usually, that's what small teams do.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-24T06:31:46Z2014-07-24T06:31:46ZEditing others tickets<div><p>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.</p></div>William Wraggtag:help.lighthouseapp.com,2008-09-20:Comment/338745702014-07-24T14:24:38Z2014-07-24T14:24:38ZEditing others tickets<div><p>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.</p>
<p>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.</p>
<p>I'm glad you found something that works for your team, and
thanks for bearing with me and having this conversation.</p>
<p>Cheers!</p></div>Julien