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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How do you use Resolution types drop-down


Do you use custom resolutions? What works for your organization?

I'm currently specifically interested in what what resolution option you use for a bug/defect logged to production that is "not a defect and works as intended"

1 comment

Yes, almost everyone I've worked with customises the list of resolutions.  As long as you don't make the mistake of using resolution for things other than "this is why we are not going to do any (more) work on this", you should use a list that tells you usefully why something is closed when you're reporting.

Usually something like "as designed" is used for "not  defect as it's working as we intended"


Log in or Sign up to comment