John Funk Community Champion

Hi Michael - Welcome to the Atlassian Community! You can create a custom field to store multiple users.

Hi Jacolene, Can you post a screenshot of the board with the issue in one of those statuses? 

Hi @Sreenivasaraju P - As you mentioned, the fields are already designated as mandatory by the red asterisk beside each field. That should be sufficient as it certainly identifies the fields. You will not be able to "highlight" the fields in any other manner. If they are that important or overlooked too often, then you…

Hi Divesh - Welcome to the Atlassian Community! Have you tried creating an Automation rule yet? If not, give that a try based on the #lookupIssues function mention in the post you cite above. 

Hi Facundo - Welcome to the Atlassian Community! You should be able to do this with an automation rule. When you update the Number Flag or Due Date field, you will use a syntax like this: {{#triggerissue.duedate}}func=plusDays({{issue."Number Flag" * 10}}){{/}} Give that a whirl and let's see what happens - hopefully I…

Hi Lee - Welcome to the Atlassian Community! That's a pretty easy fix. Just add this to your existing rule at the very top of the Description text you are placing in the field: {{triggerissue.Description}} That will keep the text that the user entered on create and then will add your part after it. Be sure to leave all of…

If that answered your question, do you mind clicking on the Accept Answer button above to close this one out? Thanks!

Is there a way to identify that it came from the portal? Maybe you could set the value of a hidden field? 

No, that should not be the project settings - when you click on that gear - it should take you to issues. 

Hey Jason, I am not following your issue. Can you give some exact examples? And maybe some screenshots? 

No, the Settings is the gear icon in the upper right side of the top navigation bar. 

Can you show some screenshots? I don't think you will be able to use the smart value above for a filter to export, if that is what you are trying to do. 

HI Aleksey - Welcome to the Atlassian Community! I would try another browser or try it in Incognito mode and see if you see the same error. Also, clear your cache! :-)

Hi @Augusto D'Amario - Welcome to the Atlassian Community! I have done this in the past, but then they locked the field. I would suggest creating an accompanying custom field with your choices and use automation to populate it, or just populated it directly. 

Hi Carlos - Welcome to the Atlassian Community! I have had various success with email to distribution lists. It all depends on the email server that hands the distro whether it will accept an email from Atlassian as such. But, yes, you can send an email to an email address not associated with a licensed user using an…

I am thinking you could create the query and then display that in a gadget in a dashboard. You would need a filter per master issue though. 

Hi Aya - Welcome to the Atlassian Community! With the Free version, you cannot control permissions. Everyone has access to everything. 

Yep, that's where I was going. :-)

Hi Alon, Can you share a screenshot of the rule details for the second trigger which is not getting fired? 

Hi Gregory, Can you share a screenshot of the kind of thing you are looking for? 

Hi Sam, That's the accountID for the user. The Jira smart value for the email will look something like: {{facilitator.emailAddress}} Not sure about exporting it, but you could use that in an automation rule that sends an email. 

Hey @Matt S - Did you ever get this working? 

Can you show a screen shot of your rule? And what is not working? Is it not firing? It fires but gives and error? Or it fires, and no error, but it does not do what you expect it to do?

Yes, that should work. 

Hi Hardip, That refers to a specific custom field (cf). The number is the id of the field. You can find the field by going to Settings > Issues > Custom Fields Click on the 3 dots for one of the fields in your list - any field. In the url address for the field, you will see the ID of the custom field. Change that value for…

Hi @DSell I can think of a couple of approaches. One is to do the clone thing as you describe in your question. However, I would link all of the tickets together when they are cloned using automation. Then setup another automation rule that when one of them transitions to another status then all of the others transition…

Hola María: ¡Bienvenida a la Comunidad de Atlassian! ¿Qué tipo de proyecto es este? Si está utilizando un proyecto administrado por el equipo, eso no es posible actualmente. Puede votar por la solicitud de función y seguirla aquí: https://jira.atlassian.com/browse/JSWCLOUD-21481

Hi Rajvi, If it is only one level deep, you might try using a select list cascading type of custom field. Or you can also use the ProForma Forms add-on.

Did you try to create the rule using your requirements?

Hi Vignesh, Where are you trying to display this count? And what purpose will you use it for?