Greetings all,
in my previous company we had always our issues assigned to the person who was responsible for the issue at that specific time , regardless of whether they were being asked for feedback/thought/informations, or they were requested to action the issue.
For example:
This can end up being a carousel of assignee changes, but I like it because everyone can see what issues are waiting for them.
Are there other recommended ways to handle this? Any suggested improvements?
TIA!
Thanks for the answer @Liam Green !
On that last assignment to the reporter I do not have a strong opinion; I see it as a way to provide the reporter with a chance to verify and reopen if they feel the requirements have not been fulfilled. Not 100% sure about this, though.
We don't often have cases where the reporter is an agent, so we don't work that way ourselves.
I can see advantages to it, as as you said the verification is a great point though. I think the potential downside is that tickets that are 'done' but waiting to be marked as resolved by the Reporter might end up sitting in the queue for a while
> I think the potential downside is that tickets that are 'done' but waiting to be marked as resolved by the Reporter might end up sitting in the queue for a while
Yup this is an issue to us, too, so I have asked my team to just close the issue, additionally leaving a comment telling the reporter they should feel free to reopen if they are not satisfied.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.