Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

New Features: Additional Done Statuses + Map Multiple Statuses per Column for Jira Software Next-gen

Hello Atlassian Community,

My name is Bryan Lim and I'm a Product Manager working on Jira Software.

Today, I'm pleased to announce the launch of two features that give Jira Software next-gen (soon-to-be-named team-managed!) workflows more power and flexibility.

  1. You can now assign additional statuses to a Done status category (for example, you can set your “Won’t Fix” status to a Done status category), so that you can accurately reflect the status of your team's work.

  2. You can now map more than one status per column on the board, and each status will be represented as a drop zone on your board’s column, so that you can keep your board tidy.

Tutorial

As your team triages incoming issues, you may come across issues that you decide you “Won’t Fix” due to various reasons (e.g., a reported bug is actually expected behavior). Now, we’ve allowed you to add additional Done statuses via the Workflow Editor:

1. Navigate to the Workflow EditorScreen Shot 2021-03-16 at 12.53.37 AM.png

2. Click on the add a “Done status” button on the top menu:

Screen Shot 2021-03-16 at 12.54.02 AM.png

3. Type in a name for your new status, press the return key, and click "Add" to add your status:

Screen Shot 2021-03-16 at 12.54.55 AM.png

4. Feel free rearrange your statuses (by dragging and dropping each status) to depict your team's workflow. When you're finished, click “Save and close”

Screen Shot 2021-03-16 at 12.55.18 AM.png

5. (Optional) Highly recommended: If you’re running sprints, please map your Done statuses to the last column. To do this, open your new “Configure board” setting via the board:Screen Shot 2021-03-16 at 12.55.53 AM.png

6. Drag and drop the “Won’t Fix” status to the Done column and delete the Won’t Fix column:

Screen Shot 2021-03-16 at 12.57.53 AM.png

7. Press save changes, and notice that the “Done” and “Won’t Fix” statuses are now represented as drop zones in the last column when you drag and drop issues on the board:

Screen Shot 2021-03-16 at 1.04.33 AM.png

 

Pro Tips

  • If your team has a lot of columns on the board and constantly find yourselves scrolling horizontally, try grouping some of your In Progress columns to simplify your board

  • If you are running sprints, we suggest you map your terminal status to the last column. A board is a representation of a team’s work; we assume that work moves from left to right as your team completes work during a sprint.

What’s next:

In the next couple of months, our team is working hard to deliver the follow workflow features:

  1. Different workflows per epics

  2. Different workflows for all issue types

  3. Ability to unmap statuses from the board

Feel free to voice your feedback for these features (or your feedback for Next-gen, in general) on this thread.

Best regards,
Bryan

9 comments

Thanks for this information about the evolving features.

With this and other changes, it will be interesting to see how Classic (company-managed projects) and Next-Gen (team-managed projects) feature sets converge and diverge...  Perhaps moving more toward a feature inheritance/override model like in competitor products.  Anything to reduce the complexity of "what works where and when and why" will no doubt be appreciated by the community of customers.

Thanks for the improvements!

Like # people like this
Vero Rivas Community Leader Mar 15, 2021

Hi @blim 

   Many thanks for sharing, is very interesting.

Cheers

Now bring back the capabilities to have transitions to specific users WITHOUT having to pay an arm and a leg for an addon!!!!!!!

Would be great to have the ability to have Epics and Version panel turned on at the same time in next-gen. Currently its a either-or, i.e in Backlog view you can either see Epics panel or Versions panel

blim Atlassian Team Mar 18, 2021

@Sarah Elmer Can you tell me a little more? Can you give me an example use case?

Blim - Been with Atlassian since 2010. Used to be able to transition to an assignee. Now cannot unless we purchase JMWE. We're a small company and can't afford an additional $500 a month for JMWE. This has caused so many problems I can't count them. Some changes are great, but older clients should be "grandfathered" in. Put a ticket in to see what can be done and got slammed by JMWE to purchase. Yeah... right.... Spent many hours on this with support and the more time I spent, the madder I got.

@Sarah Elmer Ah, interesting, unfortunately I can't speak on behalf of the Appfire developers (the author of JMWE). Would the out-of-the-box rules we provide in next-gen suit your use case? Check out these rules listed here:
1. https://community.atlassian.com/t5/Next-gen-articles/Feature-Announcement-Jira-Software-Next-gen-Workflows/ba-p/1545178

2. https://community.atlassian.com/t5/Next-gen-articles/Next-gen-workflow-transition-rules-inspiration-Assign-an-issue/ba-p/1616343

Let me know if these Rules help or not!

These new features will certainly going to be helpful at least for me. And thanks for the pro tips. I am so much excited about it.

I am curious... with all the flexibility and amazing ways you can build your own reality within your next-gen project, how will that fit with steering products such as Advanced Roadmap and Align?

It seems that these new features will cause a severe divergence, making steering very difficult on a mid- to large sized company?

This new status setup with multiple closed statuses, does that mean that next-gen projects will no longer use the resolution feature in classic projects?

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you