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,461,703
Community Members
 
Community Events
176
Community Groups

More of software engineering question -- resolution as invalid

Edited

Hi,

I have more of a software engineering question in regards to JIRA.

I find that Atlassian JIRA has "resolution" field and it can be as invalid.

Sometimes bad practices use these without any reason and that leads to many open questions.

 

Is there any way more details broad category of "invalid" sub states be defined?

Please help if you have experienced this and what can be better ???

 

I came up with below sub-states, so test and developer can work in harmony --

 

INVALID - USER ERROR

instances, where the user has totally goofed up in sending the command itself

 

INVALID - SETUP ERROR

user commands are good, but the setup is totally in a bad state

 

INVALID - CONFIG ERROR.

user is good, setup is good, but the feature configuration is totally messed up

 

INVALID - FEATURE LIMITATION

user is good, setup is good, but the feature configuration is good, but there is known issue or limitation

 

INVALID - OTHER DETAILED REASON

Something the developer/tester needs to agree upon.

1 comment

Most of us wouldn't bother with "invalid" as the rest of the phrase explains enough, user error, setup error and working as intended are often seen in the lists alongside fixed, duplicate and the rest of the defaults.

Due to bad practices, some teams members are marking valid bugs as invalid and it become ping-pong scenario of reopening.  My concern was enforce the correct reason become mandatory for marking invalid so it is justified.

Having a string of resolutions like that is not really going to help a lot.  Your people are marking things with invalid because they think it's a good reason.

Review your list of resolutions with the people selecting them.  Agree on a short but simple list that covers the main reasons something might be closed off, and then train your people to understand that any resolution means "no more work to do on this", and what they've been doing wrong with their "invalid" selections in the past.

Comment

Log in or Sign up to comment