Jira Software Support
Get started, documentation, knowledge base.
- View account
- View requests
Jira Software
Project and issue tracking
Jira Service Management
Service management and customer support
Jira Work Management
Manage any business project
Document collaboration
Git code management
Usage and admin help
Answers, support, and inspiration
System Status
Cloud services health
Suggestions and bugs
Feature suggestions and bug reports
Marketplace
Product apps
Billing and licensing
Frequently asked questions
- Log in to account
- Contact support
- Training & Certification
- Cloud Migration Center
- GDPR guides
- Enterprise services
- Atlassian partners
- User groups
- Automation for Jira
- Atlassian.com
- View in Confluence
- Manage Viewport
- Space Directory
- People Directory
How to automatically change the assignee when transitioning the workflow
Related content.
- No related content found
Still need help?
The Atlassian Community is here for you.
Ask the community
You can automatically change the Assignee when transitioning from one status to another. We'll use a workflow post-function to do this.
- Log in as a user with the Jira administrator global permission.
- Locate the workflow to edit and choose Edit .
- Click in the text field and type the name of a user, then select the appropriate user (or choose Unassigned or Automatic )
Alternative solution (using Automation for Jira)
For this alternative solution, you must have Automation for Jira installed - either Automation for Jira or Automation for Jira Server Lite (free) .
This solution might be advantageous, if you want to automatically set the assignee field through the whole project (regardless of the workflow associated to the issue type), and don't want to modify multiple workflows in the same project.
Once you have installed the add-on Automation for Jira, you can follow the steps below:
- Go to the page Project Settings > Project Automation for the project where you wish to implement the solution
- Click on Create rule to create a new automation rule
- Trigger: Issue transitioned (select the statuses from which to which you would like to automatically set the assignee field)
- Give a name to the automation rule, and turn it on
Was this helpful?
Atlassian Support
- Documentation
Discover Jira Cloud products
Learn more about Jira Cloud products, features, plans, and migration.
Integrate Jira Cloud with other products and apps
Integrate Jira Cloud with Confluence, development tools, apps, and self-hosted tools using OAuth and feature flags.
Manage users, groups, permissions, and roles in Jira Cloud
Control who has access to your Jira Cloud products and give them the right permissions to perform their role.
Configure and manage projects to track team progress
Learn how to set up, customize, and manage Jira Cloud projects.
Configure issues to track individual pieces of work
Explore issues, issue types, issue custom fields, issue screens, custom field context, and issue field configurations in Jira Cloud.
Create and manage issue workflows and issue workflow schemes
Define the lifecycle of your work and learn about issue workflow schemes and the issue collector.
System administration
Learn more on how you can set up Jira Cloud for your team.
Answers, support and inspiration
System Status
Cloud services health
Suggestions and bugs
Feature suggestions and bug reports
Marketplace
Product apps
Billing & licensing
Frequently asked questions
- Log in to account
- Contact support
- Training & Certification
- Atlassian Migration Program
- GDPR guides
- Enterprise services
- Atlassian Partners
- Success Central
- User groups
- Automation for Jira
- Atlassian.com
Configure workflow schemes
A workflow scheme defines a set of associations – or mappings – between a workflow and an issue type. As a Jira administrator, you can associate issue types with different workflows within a workflow schemes and then share this association with multiple projects.
Add a workflow scheme
Select > Issues .
Under WORKFLOWS , click Workflow Schemes .
Click Add Workflow Scheme .
Enter the name and description of the new workflow scheme.
Click Add to create the new workflow scheme.
Configure workflows for a workflow scheme
If your scheme is already associated with a single project, follow the instructions in Configuring a workflow scheme associated with a project. If you want to configure a workflow scheme shared by multiple projects, skip to Configuring a workflow scheme outside of a project. Keep in mind that changing a shared workflow scheme will affect all projects using that scheme.
Default workflow schemes cannot be configured. To change these schemes, you can create a copy or associate your projects with a different scheme.
Configure a workflow scheme associated with a project
Choose Settings > Projects .
Go to your project and click Project settings .
Click Workflows to configure your project's workflow scheme as needed.
When you're ready to publish your workflow, click Associate to begin the migration process.
Click Acknowledge and you're done.
Configure a workflow scheme outside of a project
You can use this procedure to edit any workflow scheme in the system, including those shared by multiple projects. The workflow scheme can be either active or inactive. Note that editing active workflow schemes will automatically create a draft so you don't impact existing project work.
Click Edit for the relevant workflow.
Edit your workflow scheme as needed.
Publish your draft to make your changes active.
Edit, copy, and delete workflow schemes
Check out the following options:
Associate workflow schemes with a project
Check out Managing your workflows for more information about enabling your workflow configuration by associating a scheme with a project.
Was this helpful?
Additional Help
- Configure issue workflow schemes
- Add, edit, and delete an issue workflow scheme
- Configure notification schemes
- Configure issue security schemes
Jira Software
Project and issue tracking
Content collaboration
Jira Service Management
High-velocity ITSM
Visual project management
- View all products
Marketplace
Connect thousands of apps and integrations for all your Atlassian products
Developer Experience Platform
Jira Product Discovery
Prioritization and roadmapping
You might find helpful
Cloud Product Roadmap
Atlassian Migration Program
Work Management
Manage projects and align goals across all teams to achieve deliverables
IT Service Management
Enable dev, IT ops, and business teams to deliver great service at high velocity
Agile & DevOps
Run a world-class agile software organization from discovery to delivery and operations
BY TEAM SIZE
Small Business
BY TEAM FUNCTION
Software Development
BY INDUSTRY
Telecommunications
Professional Services
What's new
Atlassian together.
Get Atlassian work management products in one convenient package for enterprise teams.
Atlassian Trust & Security
Customer Case Studies
Atlassian University
Atlassian Playbook
Product Documentation
Developer Resources
Atlassian Community
Atlassian Support
Enterprise Services
Partner Support
Purchasing & Licensing
Work Life Blog
Atlassian Presents: Unleash
Product updates, hands-on training, and technical demos – catch all that and more at our biggest agile & DevOps event.
- Atlassian.com
- Agile tutorials
- How to automatically assign issues with Jira Automation
Automatically assign created issues based on criteria in Jira
Browse topics
You can create a Jira automation rule by using an if/else condition, which automatically assigns issues to groups of users based on their issue types.
Navigate to the Automation tab of your project settings in Jira. In the rules tab, click on Create rule in the top right corner of the screen. On the New trigger screen select Issue created and click Save .
On the Add component screen, click New condition .
On the New condition screen select the if/else block option. This creates a condition that initiates an action depending on criteria in the automation rule.
On the If block screen, click Add Conditions ...
In the If Block screen, select the Issue fields condition option.
For this demo we set the condition for Issue Type > equals > Bug . Be sure to click Save .
Next, add an action that assigns bugs to a certain group of users. On the left sidebar, which has a summary of the automation rule, click the Add component text underneath the If:matches condition.
You will be prompted for a New component . Click New Action .
On the New Action screen search for and click the Assign issue option.
From the Assign issue prompt, select a user who will be assigned issues. Click the Save button.
Next you can add an if/else condition to the If:matches condition. If the condition in the If block does not match, then the rule will evaluate the Else block . Click on the Add else text on the left sidebar.
You will be brought to the Else block screen. Click the Add conditions text and select another Issue fields condition .
Add a new condition to the Else-if block . The example below demonstrates how to add a new Else-if condition that is activated when the issues type value equals Task .
Repeat the steps to add an action to the Else-if condition. The example below illustrates how to create an additional action that assigns the issue to another user.
This rule has If and Else-if conditions that checks for a certain type of issue so that subsequent actions are performed once either condition matches. Next, fill in the remaining Else condition with another action. Click on the add else text located on the rule details sidebar then click the Save button. Repeat the above steps for adding an Assign issue action to the new Else condition.
The example below reveals how to set the Assign issue action to automatically assign the issue to a user in a list.
This Assign issue demonstrates the Balanced workload assignment that automatically assigns the issue to users in the list. The Balanced workload assignment evenly distributes assignments so that a user in the list is not assigned more issues than the others. Once you configure the new Assign issue action, click the Save button.
The following screenshot details what the final rule details should look like: It should include:
1 Trigger - When: Issue created
3 Conditions - If:matches, Else-if:matches, Else
3 actions - Then:Assign the issue to x 3
Next, set a name for the rule and click the Turn it on button. In the example below, we used the name “Auto assign issues by type”. You should see the following success indicator.
Now that the rule has been enabled you can trigger it by creating some issues within your project. Try creating a Bug or Task type issue. You can then verify that the automation rule is functioning successfully by visiting the Audit log .
The Audit Log will show you the history of the automation rule from its creation and execution. If there are any issues or bugs with the automation rule, the Audit Log will highlight them and offer debugging support. If you would like to explore other examples of rules, head over to our rule template library .
Kev is a lead full stack web developer and serial entrepreneur with over a decade of experience building products and teams with agile methodologies. He is a passionate contributor, author, and educator on emerging open source technologies like DevOps, cryptocurrency, and VR/AR. In his free time, he participates in indie game development jams.
What is scrum? - A brief introduction
Scrum is an agile project management framework that is frequently used by agile software development teams. Learn about agile vs scrum and more.
Jira burndown chart: step-by-step tutorial
Master the use of Jira Burndown Charts with our comprehensive tutorial. Enhance sprint tracking and improve your team's productivity today.
Ask a question
- Jira Jira Software
- Jira Service Desk Jira Service Management
- Jira Work Management
- Confluence Confluence
- Trello Trello
Community resources
- Announcements
- Technical support
- Documentation
Atlassian Community Events
- Atlassian University
- groups-icon Welcome Center
- groups-icon Featured Groups
- groups-icon Product Groups
- groups-icon Regional Groups
- groups-icon Industry Groups
- groups-icon Community Groups
- Learning Paths
- Certifications
- Courses by Product
- Live learning
- Local meet ups
- Community led conferences
Get product advice from experts
Join a community group
Advance your career with learning paths
Earn badges and rewards
Connect and share ideas at events
- Jira Software
Automation to assign ticket to manager
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Suggest an answer
Still have a question?
Get fast answers from people who know.
Was this helpful?
Deployment type, product plan.
- jira-automation
- lookup-table
Community showcase
- Understanding Issue Types in Jira
- What are Issues in Jira
- What’s the difference between a kanban board and a Scrum board?
- New Portfolio Cloud Experience Beta
- Announcement: Project Level Email Notifications for next-gen projects on JSW/JSD
- Community Guidelines
- Privacy policy
- Notice at Collection
- Terms of use
- © 2024 Atlassian
IMAGES
VIDEO
COMMENTS
A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle, and typically represents a process within your organization. Workflows can be associated with particular projects and, optionally, specific issue types by using a workflow scheme. Jira has built-in workflows that you can use without needing to make any changes, or you can start fresh and ...
Workflows are closely related to boards. Jira admins will often match board columns to steps in the project's workflow. Teams with more complicated workflows may choose to assign multiple steps from their workflow to one column on their board to keep the board tidy. 🧹 . Ready to dig in more? Check out this Jira guide. 📚. Additional Resources:
Choose Workflows and click Add workflow. Do both of the following until you've built your workflow: Click Add status to add a new step to the workflow (you can add existing statuses or create new ones) Click Add transition or drag from a node on one status to another to add a transition. Click Publish Draft.
A workflow refers to the path your issues take from creation to completion. Each workflow is composed of statuses and transitions that your issue moves through during its lifecycle. A board is the tool used to visualize the work as it moves through your workflow. Jira administrators often set up the board's columns to match steps in the workflow.
A guide to Jira workflow best practices (with examples) With Jira you can really make the system work to your needs, precisely suiting your team's processes and requirements. You can make it yours. And the way to do that is by customising workflows. In the article I present ways to create these workflows along a number of practical examples.
To activate a workflow: Select > Issues. Under WORKFLOWS, click Workflow schemes to see a list of active and inactive schemes. Create a workflow scheme or edit an active workflow scheme. Tip: click the Active or Inactive headings to expand and collapse the list of workflows. Add your workflow to the scheme. See Configuring workflow schemes for ...
Let's take the simple process of ordering and delivering a customer's food at a restaurant and model it as a workflow: Step 1: Wait staff takes the order from the customer. Step 2: Wait staff adds the order to the cook's queue (it's placed in a queue because the cook only can start the order when they have bandwidth).
Jira Software workflows tutorials . Create a new workflow . Create and update statuses . Update default project workflows . Edit a workflow scheme . Configure your board to match a new workflow . Migrate issues to a new issue type and workflow . Share workflows . Products . Jira Software.
We'll cover Jira workflow best practices as well as some practical examples. We'll also discuss exactly why you would want to create a new Jira workflow, customized to your team's processes, and how you would go about doing so. With Jira you can really make the system work to your needs, precisely suiting your team's processes and ...
Additionally, it delves into Jira workflow examples, explaining how Jira streamlines workflows for enhanced business success. Through Jira workflow examples, businesses can see how customizable and adaptable workflows help manage tasks, track progress, and achieve objectives across different departments and projects. ... Assignment: Distribute ...
A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle, and typically represents a process within your organization. Workflows can be associated with particular projects and, optionally, specific issue types by using a workflow scheme.. Jira has built-in workflows that you can use without needing to make any changes, or you can start fresh and ...
Each Jira workflow is composed of a set of statuses and transitions that your issue moves through during its lifecycle, and typically represents work processes within your organization. In addition, Jira uses workflow schemes to define the relationship between issue types and workflows. Workflow schemes are associated with a project, and make ...
Best practices for workflows in Jira Software . Get everyone on the same page: Spend time with the team and stakeholders to understand what is important to them to gain buy-in and ensure alignment. Reflect workflow reality: Design Jira workflows to align with business processes and then decide the best fit from a workflow/issue type structure.
Solution: Advanced workflows can be tailored to: Define stages like 'Content Draft', 'Approval', 'A/B Testing', and 'Analysis'. Use validators to ensure content meets set standards before it's approved for testing. Incorporate post-functions to collate and present data post-campaign for insightful analysis. 3.
We'll use a workflow post-function to do this. Solution. Log in as a user with the Jira administrator global permission. Click on the ⚙ icon in the navigation bar, choose Issues, and Select Workflows (in the left sidebar): Locate the workflow to edit and choose Edit. If you're not in diagram mode, choose Diagram.
Anatomy of a Jira workflow. A workflow has four unique components: statuses, transitions, assignees, and resolutions. To illustrate them at a conceptual level, we'll use a well-known workflow example: that of a library. Each item a library lends out could be stored in Jira as an issue, and follow a simple workflow.
1. Testing the new workflow in separate project, or instance. Before you get your team to use your workflow, you want to check that everything works properly. To do so you can copy to your workflow to: A separate Jira project. A separate Jira site, if you have one. Either way, you want a place in Jira that doesn't impact people in the project ...
Asynchronous and focused: perfect workflows with Jira and Confluence . December 3, 2021 . ... In addition, it is possible to assign tasks to responsible persons. Use Jira and save meetings to find out who is responsible for which project and what the current status is. Intuitive commenting features ensure transparent documentation for all team ...
Keep workflows simple. Jira Work Management workflows are designed to make your work processes easier, so make sure you keep them as simple as you can. Here's an example of a simple editorial process: Start Story ideas Draft Review Final draft Final review Published. In the example above, a piece of work can only move forward in the process.
Workflow software is a centralized tool for planning, coordinating, and monitoring activities — from simple tasks to complex projects. It automates repetitive tasks, standardizes processes, and provides visibility into the status of workflows. Features like task assignments, deadline tracking, collaboration tools, and reporting help scrum ...
A - Action: Integrated JIRA automation with the customer support email system to automate ticket creation and assignment to agents based on workload or expertise. S - Situation: Manual processing of support requests led to delays and inefficiencies in the support team's workflow.
A workflow scheme defines a set of associations - or mappings - between a workflow and an issue type. As a Jira administrator, you can associate issue types with different workflows within a workflow schemes and then share this association with multiple projects. ... Change the issue types associated with a workflow. 1. Click Assign under ...
1 Trigger - When: Issue created. 3 Conditions - If:matches, Else-if:matches, Else. 3 actions - Then:Assign the issue to x 3. Next, set a name for the rule and click the Turn it on button. In the example below, we used the name "Auto assign issues by type". You should see the following success indicator.
Choose the Jira icon (, , , or ) > Projects. Select the project you want to associate your workflow scheme to. Go to your project and click Project settings. Click Workflows. You'll see which workflow scheme the project currently uses. Click Switch Scheme and select the relevant workflow scheme from the Scheme list.
How to add approval step in workflow in jira software. Ayush Pathak 3 minutes ago. I need a step-by-step guide on adding an approval step in Jira Software for issues with high or highest priority. I'm using the Time to SLA app, which should only initiate after approval from the head department is accepted. Otherwise, the issue will be closed.
Here I have a simple workflow associated with my issue. I want to know how I can obtain this workflow data programmatically via REST API. ... Essentially what I'd like to accomplish here is the ability to reproduce this workflow diagram as it's presented in jira for myself via the REST APIs. Answer. Watch. Like Be the first to like this . Share ...
I have chosen to use Jira work management for this as management need a high amount of automation written for this board to reduce workload and a simple list view that is sortable to be used by the business. Requirements: Agents are not notified of ticket creation. Team Leads are assigned the ticket on creation based on agents name picked on form.