John Funk Community Champion

Hi Zaldy, You should be able to do that if the custom field is a single user picker field. Try it as {{issue.customfield_10174}}

Hi Swati, You could try creating some variables in the rule and then use the variable to assign a numeric value for calculating.

Welcome, Geeta! We are glad you are here! What do you mean by "guide me to Jira"? Is there something in particular that you need help with? 

Hi Naqibullah - Welcome to the Atlassian Community! And congratulations on your first post! I would look at the history for the field to see if there is an entry for the field being cleared, and who it says did that if there is an actual entry. It might be that something is running either as another rule you are not aware…

Hi Rian, Yes, you can set up Automation rules to send those emails. 

Hi Patrick - Welcome to the Atlassian Community! I would say try it without the quotes. If it doesn't work, then add the quotes and try again. :-)

So you need to create a second board if you need that functionality that bad. 

Hi Alex, On the Rule Details page, make sure the box is checked under Allow rule trigger. Save and publish and then test it again. 

Hi Akshith - they are just systems fields. Curious why are you needing to know the types? 

No sure, you might post here the entire rule for those that will not let you type in the field. 

Yikes - never seen that before. That's probably going to take a support ticket with Atlassian. In the meantime, you might try updating the field using the Advanced feature. In the rule, click the More options with the down caret beside it. Replace everything in there with: { "fields": { "{{issue.customfield_10009":…

Sounds like a great decision!

You could go either way then. 

Hi Lucinda, I have not seen it do that for that low of a number. Are you using a team managed project? If so, that’s probably the reason.

Hi Salvador - Welcome to the Atlassian Community! No, that’s not currently possible. The user must be a Jira admin to modify custom fields and schemes for company managed projects.

Voted for it - thanks for sharing!

Hi @Nodar Vardiashvili - I am marking Earl's response as Answer Accepted as I believe that provides a good solution. If you still need something else related to this, please respond here. 

Hi Michael, I am not aware of any way that you can add colors to the board in the out of the box JWM board. There might be an open feature request for that already, though I couldn't find one. You can click the Give feedback link at the bottom left to make that suggestion. Another option would be to create a second board…

Hi William, What type of project are you using? Team-managed? Company-managed? Jira Work Management? I know that the Category field has been added to Jira Work Management, but it should never be mandatory. Is there any Form attached to that project and issue type that might have the Category field marked as required?…

Can you share the entire rule? 

Hi Kees, This happens when someone creates another Custom Field with the same name. This could have been done on a Team-managed project. Is your rule a Global rule? Or a Single or Multiple Project rule? 

Great! Glad you got it working as intended.

Sounds good. Glad I could help, and that you got it figured out!

You are welcome!

Great!

Yes, smart values are case sensitive. but I have never seen it do that with system fields. They have always been in lowercase like in your original question. Weird. Anyway, glad you got it to show up!

Hi Rachel, My understanding that currently only Agents should see this field and be able to raise the request on behalf of someone else. Are you seeing something other than that? Also, how would Jira know how to narrow down the list for the person entering the request, as it could literally be anyone ? 

Hi Sangeun - Welcome to the Atlassian Community! I suspect it has to do with permissions for the Request Participants field. Take a look at this article to see if something in it, or one of the links, leads you to an answer. https://support.atlassian.com/jira-service-management-cloud/docs/what-are-request-participants/

Grrrrr - was hoping that was it. Can you share a screenshot of the form as it appears in the portal when a user goes to create a new request? 

Okay, now we are getting somewhere. :-) Thank you for sharing that. So this appears to me to be a Company-managed Jira Software project and 119 is a Task issue type in the In Review Prov status which should be mapped to the In Review Prod column on the board. Can you confirm all of that? Next if the In Review Prov status…