Add 'On Hold' comment in overview filter

[Steven Plompen]

Hi , 

I've created a personal filter in which i want to add the comment of the 'On Hold' status

This way i can easily see why a ticket has been put 'On Hold'

Is this possible and which column does correspond with it as i can't find it.

Thank you!

Regards, 

Stevne 

[Earl McCutcheon · Accepted solution]

Hi Steven,

Options to see why a ticket has been put into the 'On Hold' status would require some value that is a required to be input, and this is not something that would be a default setting in Jira.  Something like adding in a required field on the transition so a user must enter a reason in that field to execute the transition.  If you do not already have this set up you would need to manually review any issue that was in the status and then look under the issue history for who executed the transition and confirm with them the reasoning.

So if you do not already have a required field set up for this you could use the following JQL to look for issues that have been in this status previously but again then requires some follow up process to manually gain the reasoning for the hold status:

project = exe and status was in ("On Hold")

To get something configured, If you're looking for a way to track a required item on a specific transition you can create a custom field specific for that requirement, set the field as required globally, then add the field to the screen used by the transition.  A good option is to use a multi select field or a select list with preset choices.

Alternatively if you want to take an existing field and make it required on a single transition, such as requiring a comment on a transition you're going to want to look at an add-on to extend this functionality, the following KB articles give examples on how to set it up using the add-on Jira Suites Utility:

• How to configure Comment field to be required in workflow transition
• How to make JIRA applications fields required in a workflow transition

Overall though I would recomend against using a variable field such as comment to add in a reason as using the comment field add's in additional manual review requirements if your trying to do JQL queries to look up a measurable data point for reporting purposes.  If you use a variable input you could really only verify if an input exists or not and then look at the data entries one at a time.  I would recomend having field with static inputs like select list so as an exe the Field named "On Hold Reason" has "reason1" "reason2" "reason3" as the options,  If you wanted to know all issues that are in on hold for reason2 you could query for something along the lines of:

status = "On Hold" AND "On Hold Reason" = "reason2"

Regards,
Earl

[Steven Plompen]

Hi Earl, 

Thank you for your answer. this will help for future workflows we'll setup but this is not what i'm looking for right now.

What i need is that i can add the 'on hold' (not required field)  value at my personal filter(see attchment)
So i can see in a glimpse why something is 'on hold'

Regards

Steven

[Steven Plompen]

screenshot filter

[Earl McCutcheon]

Hi Steven,

Looks like the screenshot you mention failed to upload, can you try to re-upload so I can take a look.

If you tried to upload the image as an attachment from an e-mail reply on the last submit I would recomend using the Insert photo option on the community portal directly just to rule out any email related issues that might have caused the failure, that can be found at the top of a comment box while your typing, located here:

Regards,
Earl

[Steven Plompen]

Hi Earl, 

That's what i tried the 1st time also , i tried again and hopefully it's loaded correctly.

Regards, 

Steven