John Funk Community Champion

Hi Tony, That is correct real time collaboration is not yet available for Jira Service Management projects. 

So as soon as he creates an issue - he gets the above screenshot for all of the issues on that project where he can't see the other functions?

Hi Josh, For automation rules, just use: {{issue.customfield_12345}} What type of field is it?

What was the problem?

Let's start with one example then. Can you post some screenshots of a workflow that you cannot edit and the error you get? 

Can you create a new issue from scratch using the Create button in the target project with all of the same values that would get copied over? 

Hi Elena - Welcome to the Atlassian Community! You need to provide some more information and examples. Are all of the projects the same type? If not, how are they different? Were they created from scratch? Or based on existing projects? Are they Team-managed? Or Company-managed? Or a mixture? 

Hi Sooriya - Welcome to the Atlassian Community! You can do that with an automation rule. 

Hi Becky, Default values apply to the Create action only - not the Edit function. 

Hola Treicy - ¡Bienvenido a la Comunidad Atlassian! Fuera de la caja, Jira no puede hacer eso. Sin embargo, podría ser posible con la aplicación ScriptRunner Behaviors.

Hi Bridget, If the users have not been added to a project role for the project, i.e. Service Desk Customers role, that might be why they are not showing up for the Reporter field for that project. 

Hi Alyssa - Welcome to the Atlassian Community! You might try setting up the single project and then create the other "projects" as Epics under that single project. Then you can link the Epics together as needed. 

Hi Krisztina You will need to add it as a Field Required Validator on the Create transition in the workflow for that issue type. 

Ah, okay. Try adding a Re-fetch issue action after the initial trigger. Or try the new Delay action! For maybe 3 or 4 seconds. Update and then test it again. 

If you see the fields in the JWM project then it’s not a Context problem. When you click the Create button and put in the JWM project, do you see the fields in that screen?

You are welcome!

So you have issues A, B, C linked to Issue D. The description for issue D changes, issue A is a match on the summary but B and C do not. What are you wanting to happen? 

Hi Amarjit - Possibly you didn't pay your bill for it or a trial ended. Go to Apps > Manage your apps.

This is what you need to try.

Hi @Kostiantyn - Welcome to the Atlassian Community! That is one of the drawbacks to the Free version - you cannot change the Permissions. So, in the Free version, no it is not possible to do what you want to do. 

Hi Angie, If you have created custom fields that have a Context associated with the original project, you will need to add the new JWM project also to the Context. And make sure the fields are on the Create screen used by the JWM project. 

Hi @kalaimani Try the Date Compare Validator in the workflow transition.

If you add the issue type only on the one project's issue type scheme, it should not affect the other projects. 

Yes, probably so. Take a look at Apps > Manage you apps to see what is there. 

Maybe try doing a Branch for Linked Issues (instead of lookupIssues), then under the branch this: If: Compare two values {{triggerIssue.summary}} equals {{issue.summary}}

You are welcome.

No, that's not possible right now. You could open a support ticket with Atlassian to have them add that functionality, but with an add-on being available, it is highly unlikely they will add that anytime soon. 

I am John Funk, and although I am originally from Nashville, Tennessee in the US, I now live in Dubai, United Arab Emirates. I like to play chess and read. 

@Osama Al-Areky - Did you get this sorted out? 

Nope, not for this.