John Funk Community Champion

Hi Mikica, Workflows are associated with Projects and then boards are associated with Projects. So if both projects are Company-managed projects, then they can share the same Workflow Scheme. If one or both are Team-managed projects, you will have to create them from scratch as they cannot be copied. 

If you added the security levels since the last time you refreshed the tab with the automation rules that might be the reason. Save and publish what you have for the rule, then refresh the page. Then see if they show up. Also make sure that the permission scheme has the actor of the rule in the Set Security Level…

Hi @Bruno Altenhofen so it is just references to these values? Or can I actually use the in the automation? For example if my automation rule looks like: Shouldn't that put the date from that question on the form into the Due date when the issue is created? Because if it should, that is not working for me. Same with Text…

Hi Prajwal, For Company-managed projects, you need to do a Move. Click on the 3 dots menu on the upper right side and select Move. Follow the prompts there, but you can change the parent that way. 

Hi Mahanth, You can't do that on the actual create. You can only designate a default security level for all new issues. But then you can run an automation rule that will change the security level based on the Reporter or some other condition. 

Yes, I would do that with automation anyway. 

Not out of the box, no. 

Hi Camila, Unfortunately, no, you cannot control that right now. I am hopeful that they will be rolling out some filter changes for the board like they have for Lists. 

Hi Paul, I would think you could achieve this with an automation rule. Make sure the tickets are linked, then have a comment added to the JSW issue be applied to the linked JSM ticket. 

It is now integrated in Jira Cloud for JSM and is available without being a separate app. :-)

Hi Prerna - Welcome to the Atlassian Community! They would need to be a licensed Jira user to see the contents of the filter. 

Isso ficará na história da questão. Se você quiser denunciá-lo, existem alguns aplicativos do Marketplace ou até mesmo algumas extensões de navegador gratuitas que ajudarão nisso. Ou você pode criar um campo personalizado e preenchê-lo com uma regra de automação ou uma função posterior no fluxo de trabalho durante a…

Hi Sensas, If you created a custom field (which both of those sound like they are) and created a context for each field that only includes the JSM project, then that might be your error. Look at the Context for each field and make sure the JSM and JSW projects are included in the Context. 

Hi Will, Take a look at this article - it might have what you are looking for. I am in the process of trying the same thing right now. https://community.atlassian.com/t5/Jira-Service-Management-articles/Reading-a-Forms-ProForma-field-value-without-the-JSON-tab/ba-p/2097012

Hi Brigette, Are you using different value for the Epic Name and Summary fields for the Epic? The Epic Link is really just the key for the Epic - something like ABC-123. It might be displaying the Summary or the Epic Name of the Epic, but the link is really just a key. So, whatever you are changing, try changing both the…

Hi @Meytal BM Following the suggestions in this post is the only way I have found to do that. https://community.atlassian.com/t5/Jira-Service-Management-articles/Reading-a-Forms-ProForma-field-value-without-the-JSON-tab/ba-p/2097012

You could add another status to your workflow and park them there. 

you betcha!

De nada!

@Shawn Murphy - Did you ever get this working? 

I Lena, It should since the issue has a value in the Resolution field. Best thing is to try it and see. 

If the field was not added to the Issue Type when you turned on the Release feature, then you probably need to contact Atlassian Support for assistance. https://support.atlassian.com/contact/#/

Since it is a Scheduled trigger - you can run it immediately to test if if you like. 

@Kees Vianen - How are you getting along with this? 

Forms can be on JSM projects also. The other option is to check the workflow. Go into Edit mode for the workflow then click on the Create transition. Then click on Validators on the right side to see what is there. 

Can you screenshot the actual rule that you have built? 

That should be the Reporter field - is it not? 

Can you share the rule that you have created so far? 

Hi Vlad - Welcome to the Atlassian Community! You might try creating some standard Stories with the information you want. Then simply clone the story when you are ready to create a new one. 

Thanks for the explanation @Nic Brough -Adaptavist- - I can see how that might happen. Though I had no idea before that scenario!