Adding Fields to the "Flagged" Screen?

[AJ Palmer]

Good Morning All,

I am curious if it is possible to add fields to the "Flagged" dialog screen. By default this screen only comes with a comments field, but I would like to add more.

I would also like to know if I can make any of those fields required on that screen
And also would like to know if I can make different kinds of flags instead of just "impediment".

All I can see is the options below. When trying to add any contexts or more options, I either see the field is locked or I literally can't find the screen this belongs too. 

[Ionut Sandu]

Hi, we are also interested to update in this screen an additional Custom Field, "Pending Reason" for the blocked issues. Is there any possibility to add additional fields to this screen? Thank you!

[Carson Price]

This is something my teams work with as well. I am curious, if you set status as "Blocked" the transition to it could have a screen that pops up asking "Why is this blocked?" or something like that. Why are people wanting to use the flag instead of status?

[Aida Selimova]

It in case you already have a lot of statuses and the issue could be blocked at each stage. So instead of complicating this use of Jira for the team it would be more "user-friendly" to add this amazing option. 

[Joey Klein]

I'm also interested in this, any way to get this done?

[Aida Selimova]

I have found temporary solution which is create a custom field with the list of reason why an issue could be blocked 

and then just created jira automations that triggers all the reasons and put Flag, so my team just need to change this custom field

[Dillon Weyer]

Great idea thanks for sharing @Aida Selimova

How do you handle capturing/updating/appending to the reason if the ticket is blocked a second time?

[Lukasz Czerwinski]

Great idea, thanks, @Aida Selimova ! 

[Aida Selimova]

Happy to share it @Dillon Weyer @Lukasz Czerwinski

Answering your question Dillon, if it´s not too late:

• if the issue no longer faces any impediments, manually update the "Blocked by" field to "no_blocks." Subsequently, the assignee will promptly receive a notification in Slack, indicating that their task is now unblocked.
• in the event of a second blockage with the same reason, the system will automatically pass through the unblocking process, either after a time gap or when the blocking reason is resolved. No changes to the blocked status occur until the issue is unblocked.
• if the issue encounters a second blockage with a different reason, the new assignee will receive a notification.

Additionally, I've implemented an extra custom field called "block comments." This field allows for the manual inclusion of comments explaining the nature of the block. This proves particularly useful in large projects with numerous concurrent issues, such as website creation, where various teams or providers may introduce multiple blocks.

While I acknowledge that the current solution isn't optimal and isn't actively utilized by my team due to its manual nature and time-consuming aspects, it still serves as a better-than-nothing interim solution. I'm actively exploring more automated alternatives and will share them here once developed.