John Funk Community Champion

Thank you for sharing. :-) And can you tell me the status of the ticket that is not showing on the board? 

Oh, no the first suggestion about having multiple single project rules would not work. But the second one should work where you use the post function and set the value of a custom field. (the field can be hidden from the screen).

I don't see anything shared. I really can't provide any feedback without seeing something. 

Hi Yaniv, Great question! I will see what I can find out, but I suspect that no you can't right now. 

@Rizky.Tuasikal It would look like this:

Great! Glad you got it figured out. 

Great!

Hi Rudy, Take a look at this previous post to see if it can help you. And maybe try {{issue.Approvers.displayName}} https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Automation-for-Jira-How-get-the-approver-value-Display-name/qaq-p/1412028

You could copy the rule and have it be a set of single project rules - that would be a fast fix. But if you need to update the rule, you'll have to do it 8 time, or update one and copy it again to 8 new rules and delete the old ones. Or you can go the route above where you set a custom value in a transition post function. 

Hi Raz - Welcome to the Atlassian Community! You can do that with an Automation Rule. Create a Scheduled Trigger rule to run once a day. Put your JQL in the scheduled trigger. Then add a new action for Transition Issue and select the status you want it to transition to. Make sure there are no Conditions on the transition…

Ah, thanks, David! Cleaning up my syntax mess as usual haha. 

You are welcome. 

Make sure the field is on the Create screen used by the project. 

Hi Joe, I would try the Build-your-own (scripted) Validator (JMWE app). In the Jira expression section select issue fields and search for Reporter. Select the value for issue.reporter.accountID then add != after it. Then select Lookup user and search for the generic Slack user. Select insert accountID. So it should look…

Hi Mübeccel - Welcome to the Atlassian Community! Can you posts some screenshots of what you are seeing? (Please obscure any sensitive data). 

Hi Daniel - Welcome to the Atlassian Community! Configure your security levels as normal, then create an Automation rule that sets the value of the Security Level based on the value of the Location field. You probably want to use an Issue Created trigger, then add a Condition for Location = USA and then an action for Edit…

Hi Jordan, First, there is no "Move" function in Automation for Jira. You can clone the issue and then the issue will show on whatever board that is met by the board's filter. Second, the error you are getting says that it can't Clone the issue because the actor of the rule doesn't have permission to create an issue in the…

Hi Liza, First, I guess, why would you do that? The reporter should be the person submitting the request. But, one option would be to put the Reporter field in a Hidden field in the Request Form. I have not tried that so note sure that it would actually work. Another option is it create a an Automation rule that fires on…

Hi Phil - What do you mean by "run a subtask"? Can your describe in a little more detail what you are trying to do? 

Hi Ken, You need to add a Context to the Custom Field to attach it only to the Purchasing issue type. Got to Settings > Issues > Custom fields Search for your custom field and click the 3 dots menu to the right and choose Contexts and default value There you can add the issue type. 

Hi David, Yes, you can do what you initially describe above, except that I would see no need to keep the initial JSM issue open. Just auto close it when it creates the JWM issue and let all of the communication happen within the JWM issue. That's all assuming that everyone involved are internal users and all have a Jira…

Hi Timothy, Make sure that both fields are on the Create screen for the project you are cloning to. Also, you might want to consider the Deep Clone app from the Atlassian Marketplace. 

Hi Jun, With the end of life for Jira Server maintenance coming up and no new licensees being sold for apps, I am not sure what your options for Server might be right now. Your best best would be to migrate to Jira Cloud and use the Advanced Roadmaps function on the Premium subscription. However, this article might be…

This is a duplicate of https://community.atlassian.com/t5/Jira-Software-questions/Can-I-see-issues-of-different-projects-as-a-hierarchy-style/qaq-p/2256451

Hi Prabhu - I am marking this as Answer accepted since Bill's response should meet your need. If not, please post back with any additional problems you are encountering with implementing his suggestion. 

@Alex C @Valerie Lytko - please post as new questions so that they can be dealt with individually according to your unique needs and so more people will see them. Feel free to tag me on the new questions if you like. 

You are very welcome. 

Glad you found the answer!

Hi Logan - Welcome to the Atlassian Community! I suspect that the new email might have gotten blacklisted for some reason. You should open a support ticket with Atlassian for them to check it. Please post the resolution back here. https://support.atlassian.com/contact/#/

Hi Neill, I suggest you contact support at the vendor and ask them if they are indeed adding that issue type. They should be able to tell you how to stop that if they are.