Here is the use case: the project team does not want to have the default assignee to an individual because people may not know who is in charge.
They want some kind of generic account like "Defect Coordinator", an account that does not solve the issues itself but that it is in charge of assigning them to the right person.
This person may change from time to time, for example when the original coordinator is in vacation.
I would prefer not having to add a local-directory account as I am using LDAP authentication and trying to keepthe local account to minimal -- I may need "defect coordinators" for lots of projects.
Another reason why I do not want to use local account is because it would require administrator access to change the email adress of this user and also because I do not want to have multiple accounts sharing a single email address.
How are you dealing with this?
Hmm. I don't think you can. You've ruled out "dummy user with changing ownership" and "changing ownership between individual humans". You've got to do one or the other.
This isn't even a Jira question really, it's about process. Iissue X needs to be owned by Y, where Y can be anyone, but only one person at a time. You either have to have a flag for the current user to carry (change user as needed), or a single point of contact with a redirect (dummy user).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs