Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Adding Fields to the "Flagged" Screen?

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. 



1 answer

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!

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?

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. 

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

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

jira flagged.png

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

Like Pier-Luc Boucher likes this

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?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events