Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,165
Community Members
 
Community Events
176
Community Groups

Next-gen best practices for 'Canceling' an issue / enforcing field completion?

Hello, 

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.


2 answers

I notice you can how set multiple 'done' (i.e. final) statuses.
So you can have one end column on your board with 1 or many final statuses. 
I did this by:

  • edit workflow
  • add a 'done' status of cancelled

Then on settings > board > Columns and statuses:

  • Drag the new cancelled status to the 'DONE' column, and deleting the cancelled column

Hi @Ian thanks, this helps me closed the sprint while having the status correctly

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
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events