This is unfortunate :-( Also unfortunate: I have just enough permissions to mess it up and not enough to fix it. You can follow https://issues.apache.org/jira/browse/INFRA-20563
By the way, does anyone really use the difference between "Resolved" and "Closed"? Since I am talking to Infra and probably getting our workflow re-initialized manually, we could simplify those to a single state and let the Resolution field be the one source of truth for the nature of the resolution. (typically I think fixed things get "resolved" while wontfix issues get "closed" - this is not actually what the difference is supposed to be) Kenn On Thu, Jul 23, 2020 at 9:43 AM Brian Hulette <[email protected]> wrote: > Yeah same for me. Not a huge deal.. I just noticed that the jira UI isn't > rendering references to my closed tickets with a strikethrough, and I'd > like to distinguish others as "won't fix" or "obsolete". It should be easy > enough to backfill these once this is sorted out though. > > Brian > > On Thu, Jul 23, 2020 at 2:01 AM Maximilian Michels <[email protected]> wrote: > >> I can close/resolve but it will show "Resolution: Unresolved": >> >> On 23.07.20 02:30, Brian Hulette wrote: >> >> Is setting the Resolution broken as well? I realized I've been closing >> jiras with Resolution "Unresolved" and I can't actually change it to >> "Fixed". >> >> On Tue, Jul 21, 2020 at 7:19 AM Maximilian Michels <[email protected]> >> wrote: >> >>> Also, a friendly reminder to always close the JIRA issue after merging a >>> fix. It's easy to forget. >>> >>> On 20.07.20 21:04, Kenneth Knowles wrote: >>> > Hi all, >>> > >>> > In working on our Jira automation, I've messed up our Jira workflow. >>> It >>> > will no longer prompt you to fill in "Fix Version" when you resolve or >>> > close an issue. I will be working with infra to restore this. In the >>> > meantime, please try to remember to add a Fix Version to each issue >>> that >>> > you close, so that we get automated detailed release notes. >>> > >>> > Kenn >>> >>
