Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
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

Next-gen: resolve issue before transition final column

My team is being asked to add specific statuses, only valuable to our QA team, into our board, creating clutter. I am looking for a way to mark an issue as done before it hits the final column in the board. Trying to do something like have DONE be in the middle and keep all the QA stuff on the far right where we can ignore it.

Until we can control when resolution is set, are there workarounds anyone has used?

4 answers

0 votes

Hi Alexis,

Thanks for reaching out to Atlassian Community!
Currently, since next-gen projects don't have the option Board settings and the projects being independent of other Jira settings, it's not possible to set a category for the statuses on the board. On next-gen, the first column will be "To Do" and the last one the "Done" that has the resolution. All other statuses between those two will be "In progress".
For now, there is no workaround for that. If you and your team needs the option, we suggest using a classic project.

Regards,
Angélica

Hello @Alexis Isabelle . 

 

As I "tested" the new next-gen project, I found that you can set some rules for the board.

So, for me this is very helpful. For example, on our projects we have the next columns:

To Do

In Progress

In Review

Testing

Testing OK 

+ other 3 columns

Next to the "Complete sprint" button you have 3 dots to manage some rules, there are only 2 rules available Assign an issue to someone and Update an issue field.

I used the first rule to assign to myself the issues that are moved to "Testing" column, because I do the testing, and for the second rule you can update an issue field to mark it as done ( from someone's part) or you can add a field option ( with multiple options depending on what you want to select). 

You can add new fields for tasks, this is good. So you can use a specific field added to an issue to manage a rule when updating an issue. 

Maybe this helps you:

I added a new field with 3 options ( on issue types)

I added a new rule to update an issue field when I move the task in a different column. And the field added on issue type appear on what kind of field you want to update.

So you can to this with each column you want

TP board   Agile board   Ninja Coders (1).png

 

Good luck ! :) 

Hello @Alexis Isabelle . 

As I "tested" the new next-gen project, I found that you can set some rules for the board.

So, for me this is very helpful. For example, on our projects we have the next columns:

To Do

In Progress

In Review

Testing

Testing OK 

+ other 3 columns

Next to the "Complete sprint" button you have 3 dots to manage some rules, there are only 2 rules available Assign an issue to someone and Update an issue field.

I used the first rule to assign to myself the issues that are moved to "Testing" column, because I do the testing, and for the second rule you can update an issue field to mark it as done ( from someone's part) or you can add a field option ( with multiple options depending on what you want to select). 

You can add new fields for tasks, this is good. So you can use a specific field added to an issue to manage a rule when updating an issue. 

Maybe this helps you:

I added a new field with 3 options ( on issue types)

I added a new rule to update an issue field when I move the task in a different column. And the field added on issue type appear on what kind of field you want to update.

So you can to this with each column you want

TP board   Agile board   Ninja Coders (1).png

Good luck ! :) 

Hello @Alexis Isabelle . 

As I "tested" the new next-gen project, I found that you can set some rules for the board.

So, for me this is very helpful. For example, on our projects we have the next columns:

To Do

In Progress

In Review

Testing

Testing OK 

+ other 3 columns

Next to the "Complete sprint" button you have 3 dots to manage some rules, there are only 2 rules available Assign an issue to someone and Update an issue field.

I used the first rule to assign to myself the issues that are moved to "Testing" column, because I do the testing, and for the second rule you can update an issue field to mark it as done ( from someone's part) or you can add a field option ( with multiple options depending on what you want to select). 

You can add new fields for tasks, this is good. So you can use a specific field added to an issue to manage a rule when updating an issue. 

Maybe this helps you:

I added a new field with 3 options ( on issue types)

I added a new rule to update an issue field when I move the task in a different column. And the field added on issue type appear on what kind of field you want to update.

So you can to this with each column you want

TP board   Agile board   Ninja Coders (1).png

 

Good luck ! :) 

Hello @Alexis Isabelle . 

 

As I "tested" the new next-gen project, I found that you can set some rules for the board.

So, for me this is very helpful. For example, on our projects we have the next columns:

To Do

In Progress

In Review

Testing

Testing OK 

+ other 3 columns

Next to the "Complete sprint" button you have 3 dots to manage some rules, there are only 2 rules available Assign an issue to someone and Update an issue field.

I used the first rule to assign to myself the issues that are moved to "Testing" column, because I do the testing, and for the second rule you can update an issue field to mark it as done ( from someone's part) or you can add a field option ( with multiple options depending on what you want to select). 

You can add new fields for tasks, this is good. So you can use a specific field added to an issue to manage a rule when updating an issue. 

Maybe this helps you:

I added a new field with 3 options ( on issue types)

I added a new rule to update an issue field when I move the task in a different column. And the field added on issue type appear on what kind of field you want to update.

So you can to this with each column you want

 

 

Good luck ! :) 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,255 views 10 14
Read article

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