When a customer reports a bug using the portal, Jira Service Management assigns the request to your organization's Bug workflow. By default, this workflow is the same for both Jira Service Management and Jira Software issues.
This workflow follows the basic process above. Jira administrators can customize it to adapt to the needs of your customers, developers, and service desk agents.
Jira's default Bug workflow is a good starting point for most teams. As your organization grows, you may want to update your workflow to suit the specific needs of your business. For example, you can add steps for approvals or QA verification.
You need to be a Jira admin to make changes to workflows. Changes to workflows affect all projects that use the workflow. Be careful!
To edit the bug workflow:
Read more about working with workflows.
You may want to add a stage to your bug workflow for when a development team investigates the issue. This status helps your service team track which bugs are being handled by a development team. And, it informs customers when the issue is being looked at by developers.
To add a new step in the workflow:
To add an incoming "escalate to development team" transition:
To add a transition to allow the agent to mark the request as done:
Publish your draft workflow.