Hello i have a question to Resolution field. I do not really understand which is his use. Since i already have statuses like closed and so on. Why do i still need a Resolution field. Could you explain me the use of this Field and what i have to take in concern when using it ?
In addition to the other answers, be very careful with the field. A couple of simple points about it:
If you don't want to use resolution at all, then teach your administrators to hide it, but build workflows that set it (and clear it) at the right points.
As Mike has mentioned above, a resolution lets users know what a particular issues was closed e.g. Fixed
This resolution might be used for a Bug issue type for example.
When a resolution is set on a issue it puts a strikethrough on the resolved issues.
This allows users to visually see what issues are resolved.
Dear @Corinna as @Mike Friedrich mention is very correct way , but that can used it multiple way.
We are using resolution field for getting issue from different projects.
Suppose 2 projects we are getting with different workflow.
w1 = Pending - Ready for Review - Design - In Progress - Review - Testing - Closed
w2- Open - Design - Implemention - Manager Review - Closed
So we are consider W1- W2 Starting 2 transition is As Pending next 2 transition as In Progress and last transition consider as closed.
now we want Status Which is still in pending ..
as writing query and reminding all status with big workflow we are using resolution field as group of some status.
so we can get value easily.
A developer should never just close an issue he thinks he solved. Instead the issue will usually go to the "Resolved" status so QA can verify and close. Resolution tells you WHY the assignee thinks the issue is no longer his or her problem. e.g. "I fixed this" would be resolved with the resolution Fixed. "There is no problem here" would be resolved as Not an issue. "We have another issue that describes the same problem" would be resolved - duplicate. "This is not a good idea" would be resolved - wontfix. Before closing the issue, QA will examine the resolution and know whether to test a fix or not.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs