Mikael Sandberg Community Champion

The copy is only if you are copying between different issues, you cannot use that to copy fields within the same issue. In that case you have to use smart values in order to do the copying.

Hi @Matthew Brandabur, Welcome to Atlassian Community! What the Copy screen is showing is that a page can have a parent, not that a space can have a parent. Nested spaces is not a thing in Confluence. According to this suggestion, CONFCLOUD-1095, it is not something that is being considered either. 

Your edit issue field should look something like this: Just replace the smart value I'm using with {{fieldChange.fromString}}

Hi @David Allen, Welcome to Atlassian Community! Currently it is not possible to have link types that are project specific without using an app like Issue Matrix or Linksy. There is a suggestion, JRACLOUD-16325, that you can vote and follow. Based on the latest update this is not something that is being prioritized in the…

What does your edit issue field look like? 

- daniela.toledo@claro.com.br I am part of the EAP and can confirm that the interface currently looks the same as in Atlas, so currently nothing is changing just the way you access it.

If you have added users with the trusted role they will get full product access to all your products but are not added to the product group. The same thing applies to users that are added as site admins.

Hi @Marcie Talbot, Welcome to Atlassian Community! Users that have access to JSM as an agent are added to the group called jira-servicemanagement-users and if you look up that group you can see who have access. 

Hi @Jeremy Wortsman, Welcome to Atlassian Community! You have a couple of options to do this, one is to link the field to a Jira field and then use that as part of your automation to lookup the object. Another option is to use smart value to get the field value and then use the smart value as part of the lookup. Have a…

Hi - daniela.toledo@claro.com.br, Welcome to Atlassian Community! Yes, it was announce during Team 24 that Atlas will become part of the Atlassian Platform Experiences. It is currently in EAP and you can learn more about it here.

Hi @David Canuso, Welcome to Atlassian Community! The behavior is expected, once you submit a Form with linked Jira fields the Form will not be updated if you make changes to the fields. You would need to open up the Form for editing, that will update the Form fields and then you have to submit the Form again. 

You can do that by using smart value, {{issue.key}} and {{triggerIssue.key}} would give you the issue key. Which one you should use depends on how you automation looks like, as long as the focus is on the initial ITSM issue then {{issue.key}} will do.

Hi @paloma.garciadelgado, Welcome to Atlassian Community! Currently conditional logic in forms is only supported in JSM projects, but it is coming to Jira in the near future as announce in this article. 

As you stated, these accounts are associated to apps that you have installed and are used so that the app can perform their functions. When the vendor creates the apps they pick the permissions that are needed in a space, so you would have ask the app vendor why they would need to be space admin.

Hi @Chris Cashman, Welcome to Atlassian Community! You can connect multiple channels to a single JSM project, have a look at this KB for more information. So what you are trying to do is possible.

Hi @Nick Jones, Welcome to Atlassian Community! The aqlFunction() can only be used on Asset object custom fields and that is why you get an error when trying to use it with assignee. One way around this would be to have an asset object field that is set when the assignee is set so that you can search on the object.

@jd_santos You have to access the project from the Portal, if you do it from within Jira then you will only see the project key. Another option is to export a request to xml format, the project Id will be at the top in the file.

As @Marc -Devoteam- mentioned below you can create/delete API tokens, but that does not help you with changing the tokens in your automations...

Hi @Ahmed Mohamed, Welcome to Atlassian Community! The short answer is no, currently there is no REST API that would allow you to modify an automation. There is a suggestion, AUTO-51, that you can vote on and follow.

Hi @Amanda Pettersson-Dahlin, Welcome to Atlassian Community! Yes, you can join the EAP and only enable it on your Sandbox instance. If you read the KB about it it is mentioned that the EAP has to be enabled on each instance you have. When we joined I think it stated that you could only do it on a Sandbox environment due…

Hi @Katherine Nevitt, Welcome to Atlassian Community! The easiest way to access resolved/canceled requests is to create a filter, and your JQL would look something like this: project = <project name> AND statusCategory = Done By using a filter you can do bulk changes to the requests. 

You could either use epics and tasks, or the other option would be to use issue links and link tasks that are related.

Hi @Tanya Courtney, Welcome to Atlassian Community! The short answer is no, subtasks cannot belong to a sprint separate from its parent. Same thing applies if the parent is in a done status and the subtasks are not, you will not be able to close the sprint. 

The error you get is expected, the was operator can only be used with Assignee, Fix Version, Priority, Reporter, Resolution, and Status. Instead you would have to use the {{fieldChange}} smart value in order to get the previous value of the field.

You have a couple of options, one is as you mentioned using an issue type for OOO that the automation is checking. Another option would be to use the on-call schedule in Operations, but you would then need to use a third-party app if you have more than one person on-call at the same time, I wrote about it in this article.…

Yes, the branch will iterate over each issue returned by the JQL, it has the same affect as adding the JQL to the initial schedule trigger.

In the new schedule component the JQL is hidden until you click the checkbox at the bottom that allow you to run a JQL

The warning you got in the first version of you automation is because it is expecting the JQL to be part of scheduled trigger component, similar to this template:

Hi @subratsahani, Welcome to Atlassian Community! Your query would look something like this: creator = currentUser() AND reporter = <user created on behalf for> When you use the created on behalf of you will be the creator and the reporter will be the user you created the request for.

You will only see issue types that are available for company-managed projects in the screen you attached. Issue types created in a team-managed project will not be visible here, they are only accessible from within the project. If you go to the project you created, or go to Projects it will tell you if the project is…