Whenever we edit an issue in Greenhopper plan mode (maybe others to), not inline, but by pressing "e" on the keyboard for instance, resolution is set and the key has strikethrough. This has not been the case earlier. The field "resolution" is required so it automatically sets it to fixed.
This does not happen when we do inline editing on say description or is we edit the issue in Jira.
Has anyone else had this problem?
This is what we have:
* Atlassian GreenHopper (v6.1.6)
* Atlassian JIRA (v220.127.116.11#846-sha1:7ae4d02)
Yeah, this is definitely the easiest way to do it (and to add custom post-functions to help better manage your workflows).
I use it in a Test Case workflow to automatically clear the value when we fail things (sets back to open in the dev project) and passed when we pass something. Now all my team has to do it log work :D
Yes, well, that is not really the problem here. I am not trying to do a transition, the bug occurs by just editing the issue. I don't want to add fake transition just to "purge" the resolution field for every step in my workflow.
Maybe this is not the right place to ask this? I suspect that this is a bug, but I wanted to make sure before I filed an actual one.
Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot