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

Your Points Tracker
  • 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
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?
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 best practices for 'Canceling' an issue / enforcing field completion?


After migrating to a next-gen project then discovering the severe limitations to basic functionality, I figure I'd ask the community. After all, Atlassian wouldn't put out a product to their customers that was just completely missing solutions to their most common needs... right? 

1) Canceling issues

We all know that issues are not always completed successfully. Classic projects had obvious solutions to address this that next-gen removed entirely. Now we are only allowed a single 'completed' status.

What is the best practice for canceling a ticket (please don't say 'delete it')? Is there one that doesn't involve extra fields and unnecessary extra work for users compared to classic? What's Atlassian's thinking behind not supporting a 'Cancelled' status in next-gen?


2) Required fields

Every field I have on my issues are relevant and should all be completed by the time an issue is completed. Some should have been filled in immediately on creation, some have clear checkpoints where they should have been confirmed filled in prior to moving to a new status. Some could have been filled in automatically, but unfortunately next-gen is severely limited with its rules / automation abilities. 

So what is the best practice in next-gen to ensure users fill out the fields they need to?

Currently I see no way to restrict progress or creation of a ticket based on field requirements. In fact, the only way I see to make sure all the fields are filled in is MANUAL REVIEW. As in, I literally need to search through the issues field by field to check for blanks and follow up with the issue owner. You cannot be serious.

1 answer

I'm trying to figure this out as well. Any input is greatly appreciated. I as well would prefer not to have to delete the task but mark it as canceled. 

As you can see, Atlassian support/community is not the place to go to find help. 

The standard fields in classic projects are not available in parity in Next Gen projects, so you can't see/use the Resolution field that would be tied into various processes. I ended up making my own version of it.

As to making fields required... nope, you just don't have the option. It really is that bad.

Suggest an answer

Log in or Sign up to answer
Site Admin
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,152 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