Like many companies, ours is no different; we have a ticket queue from which developers can take and complete a ticket. Sometimes, however, the developer has a question that needs answering. Essentially, we would need a method by which we could "pause" an issue or put it "on hold". My company will not pay for any additional plugins/addons, however, we do have scriptrunner and a few others that makes workflow creation and editing very smooth.
What is the best practice for putting an issue on hold. I would think it would work similar to the following:
create issue-->developer pulls ticket--> developer either cannot continue without having a question answered or he is pulled off of his existing ticket for an emergency--> developer transitions ticket to "on hold" status. Reports can then be run by that status.
Is there a better method?
As the flag highlights the issue instead of sending it to the background I would rather use a label for that.
But generally we design the workflow with a "hold" status and ask for a date (required) and user (optional) during the transition there. When the date is reached the issue will be moved to open and assigned to the selected user (if one was selected).
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.