How come you cannot set Resolution on columns other than Done?

[Jack Kora]

I really like the next-gen simplified Jira. The UI is better and most of the complex features that made the classic Jira so difficult aren't needed for a lightweight process. And I love the Roadmap feature!

However, every single team I ever worked on needed to close issues with the status of Won't Do. It's just how life works - some things you do not work on. 

So how come when you create new columns on the board you cannot create a Won't Do column and have it set the Resolution on the issue???

Because of this single omission I had to stay on jira classic. And I don't even see this feature in the roadmap.

[Deleted user]

The user used an addon which ran a JQL query under their persona as a search context. Talk to the user, monitor the logs, oh, perhaps LogTailer if you're bored of rdesktop/ssh, anyway, monitor for a repeat of the user doign their thing, narrow where its coming from, locate the addon in question.

[Khanh Nguyen]

thanks for the idea - can you help clarify what you mean by "The user used an addon" ?? not quite sure I understand what this is? Thanks again

[Deleted user]

JQL queries do not happen in isolation, they run in the context of a user (permissions etc), therefore, a user may have accessed a feature (possibly contributed by an addon, possibly JIRA itself) that ran a query, or has data that caused that query to run.

JQL queries are not just for search filters, they are used through JIRA for filtering and retrieval.