You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello Atlassian Community!
Are you tired of chasing down your teammates for missing information on your team’s Jira Software Issues? From creation to completion, a team’s work item needs to capture important information throughout its lifecycle. Today, I’m proud to announce: team-managed project admins now have the ability to make fields* required upon issue creation.
As you’re following along with the example, consider: what information does your team need to capture when an issue is created?
Let me introduce you to Acme, Inc: a fictitious e-commerce company that has 350 employees. Acme is gearing up to launch a new website and they have a cross-functional product team of eight individuals working on this project. Let’s take a look at how the team at Acme uses required fields to help them deliver the new website.
Emma joins the product team as a lead software engineer and familiarizes herself with the ongoing project by viewing the team’s backlog for the first time.
1. She first notices there are a couple of bugs the team needs to prioritize.
2. Emma starts by organizing the backlog by dragging and dropping which pieces of work she thinks is highest priority. Driving revenue is important to the business, so she ranks the checkout button bug at the top.
3. After Emma finished prioritizing that bug, she reflects and realizes it would be helpful to classify the priority of each bug to ease the prioritization process as the backlog grows.
Emma checks with her team and the team agrees each bug should be assigned a priority. So she navigates to project settings, adds the priority field, and makes it required.
4. She tests the creation of a new bug and notices the priority field is now required. Her and her team now save themselves the time of chasing down the bug reporter to understand the priority of each bug.
5. Emma also notices it’s easy to edit the priority of past bugs inline and is thrilled she didn’t have to open each and every bug.
6. Next, Emma wants to keep a close eye on all incoming bugs, so she wants to be assigned to each incoming bug. She does this by first navigating to the workflow editor, selecting the initial transition, clicking “Add rule” on the right menu bar.
7. She then selects “Assign an issue” from the rules list and then selects herself from the dropdown menu.
8. Emma proceeds to save her changes to the bug workflow.
9. All newly created bugs are now assigned to Emma so that she can immediately triage them upon creation.
Start simple and set up one required field, then iterate with your team going forward.
Use inline actions to save your team time when grooming the backlog.
Set rules to help automate and make your team's process more efficient.
How do you and your team ensure that the correct info is captured on each Jira issue? What rules or automations have you set up to make your team more efficient? Share below in the comments!
*The current default required fields include: Summary, Issue Type, Project ID and Reporter