It's fine if you want to mark this as "Closed" to indicate that you're not thinking about it anymore.

Using the resolution "fixed" here though is very clearly incorrect since nothing about this was "fixed". The one you're looking for here is "Won't Do" as in "we see this ticket, but we're not doing it".

Two other thoughts?

1. This is the exact use-case for resolutions in JSM projects, including team-managed. Right here. On this ticket.
2. As 8f68c03058ab says, status category doesn't even come close to solving the problem. We already know it's done - the question is why.

It is also not possible to use more Statuses in the "Done category" in Next Gen, eg Done, Lost, Canceled.

For Next Gen - "Resolution" name is reserved by Jira, use eg "Resolution type". But it won't help you much.

If you put a workflow condition for filling in the "Resolution type" field, then it will only restrict Status in the Board, but you will not know why (there is no warning).

Original Resolution is also set during the transition, although it cannot be affected.

ك

Hello,

My name is Christophe Capel, I’m a Product Manager working on simplifying Jira Service Desk’s project configuration.

In Jira Service Desk next-gen we've decided to focus on using status categories so that when a request is done, it's done. There is no resolution in Jira Service Desk next-gen out of the box (which differs from Classic).

If your organization requires a resolution to be set for a specific workflow when the request gets done, you can easily create a resolution field for the specific request type using a custom dropdown field.  You can either mark it as required or not. If you mark it as required, you will need to set a default value, e.g. unresolved.

I am marking this ticket as resolved.

Cheers

Christophe