Hi there, How I should categorize JIRA ticket as: Defer for Later Fix.

[Dhan Singh Bisht]

We are still waiting for an answer to the issue. For now, we need to categorize the JIRA ticket as: Defer for Later Fix and proceed with the next steps. Please let me know how I should do it.

[Tomislav Tobijas]

Hi @Dhan Singh Bisht ,

You could use several methods for something like this:

1. Add new resolution - is "Defer for Later Fix" represents a final state for the current work cycle, you can add it as a Resolution.
2. Use Labels - If you want to categorize the ticket without changing its status or resolution (easiest option if you ask me)
3. Create custom field - for example, you can create a Dropdown or Radio Button custom field.

However, all of that relies on internal processes and how your current system is designed. I would recommend reaching out to your internal Jira admin to check with them if they have any ideas on how you would 'construct' something like this. 👈

Cheers,
Tobi

[Dhan Singh Bisht]

@Tomislav Tobijas - I appreciate your guidance.

I have reviewed this again and I believe adding "HFN ||" at the beginning of the Issue Summary to indicate Hold for Now. This should clearly communicate to the team that it is a valid issue and will be addressed at a later stage.

Please let me know if you agree with this approach.

[Tomislav Tobijas]

That+s one way to do it, for sure @Dhan Singh Bisht 
And it can be effective too (if used appropriately). It kinda depends if you need to do some advanced reporting or not. If so, I would still go with custom fields or resolution, as you can only select an option and not rely on users to type in the correct prefix.

If talking about this approach, you could also automate it with something like (build an automation):

1. Trigger: Choose Work item Transitioned (e.g., when moved to a "Hold" status) or Work item Edited (e.g., when a specific label is added).

2. Action: Use the Edit work item action for the Summary field.

3. Smart Value: Use the following syntax to prepend the text without overwriting the existing summary:
   HFN || {{issue.summary}}

You can get an idea.

But yeah, that's one way to do it.

[Arkadiusz Wroblewski]

@Tomislav Tobijas In my opinion, automation is almost a must-have for this. A summary prefix is easy to see, but it can also become inconsistent very quickly.

[Dhan Singh Bisht]

@Arkadiusz Wroblewski and @Tomislav Tobijas - I appreciate you both for your suggestions. I will discuss with my technical team and will see what we can do better to resolve it. Thanks again!