Mikael Sandberg Community Champion

Okay, so add .name to your smart value and that should give you the name.

You need to remove field from your smart value, it should look like this: {{issue.customfield_10206}}

See it as a way of creating your own teams that you can use for @ mentioning instead of @ mentioning individual users. And my guess is that once Atlas and Atlassian Together goes GA it will play a bigger role.

Yes, on Server/DC you can open it up for anonymous access, this is not possible on Cloud, mainly because it is considered a security risk to allow anyone with internet access to be able to get to your instance. 

That's because the default permission scheme says that anyone that can log in can be added as a watcher or be @ mentioned. But that doesn't mean that they will have access to those issues. In order to access an issue in JSW/JWM you have to be a licensed user.

If you go to Products and then click on your instance under Sites and Products on the left-hand side, that will take you to Site settings, from here you should see Jira Service Management and Portal customers on the left-hand side.

They would need to be assigned a Jira license, having access to the instance is not enough, that only works in JSM, for Jira Software/Work Management you have to have a license. This is the difference between JSM and JSW/JWM, in JSM it is only the agents that needs a license, anyone that is added as a customer can access…

Hi @Chris Lynch, Welcome to Atlassian Community! You can see all your customers if you go to admin.atlassian.com, select your organization, then go to Products > Jira Service Management. From here you can manage all JSM customers. 

If you want to know the customer/reporter, then your only option is to use a custom field on the Jira side and add the name/email to it. You can get the name by using the smart value {{reporter.displayName}}

The only way this would work is if the customer/reporter on your JSM request also has a Jira license. The reporter outside of JSM has to be a licensed user. And this is the reason the reporter is not carried over and replaced by Automation for Jira.

Hi @Michael Cropper, Welcome to Atlassian Community! Teams is part of Atlas, that was just announced to be available for everyone today, and as part of Atlassian Together that was also announced today during Atlassian presents Work life.

No, in this case it only informs them that the request has been moved and if they need more information to contact the team via Slack and replies are not monitored. The internal issue has a link to the request so if the customer mention the request they can find the internal issue via the link.

You can do this via automation, I have a couple of teams that does this. They use JSM as the intake and once moved to a specific status, or right away, makes a copy or clone the request into an internal project. Here is an example that clones the request and closes it with a comment:

Even if you turn on the auto-scheduling you still have to review all changes before it is being synced over from Advanced Roadmap to Jira. The reason behind this is so you could create different scenarios in Advanced Roadmap without making changed so the actual issue itself.

Hi @KEERTHI K, Welcome to Atlassian Community! Any changes made in the plan are not automatically synced over to Jira, so if you want to revert a change that is possible from the Review changes up in the right-hand corner. 

Hi @Vadim Nadtochaev, Welcome to Atlassian Community! Yes, that is possible. What you need to do is create new permission scheme that only allow users in a specific role or group to browse projects apply that to existing projects. I would recommend using project roles because that allows project administrators to give that…

Make sure that your workflow allow transitioning from In progress to your destination status without and problem or that it doesn't have a screen with required fields. If for example you have Resolution on a screen that takes you to Done, then Resolution is required.

Did you change the epic name or just the summary? What is shown in the drop-down is the epic name.

Your automation would look something like this (except for the add comment):

Hi @Wagner Thierry, Welcome to Atlassian Community! Yes, that is possible and is fairly simple to do. Your automation should trigger on the transition to the last status on your Kanban board, then clone the issue into the project for your Scrum board. If both boards are in the same project then you just have to make sure…

I believe scriptrunner can change the issue type, I know that it has that function in Data Center.

Hi @Administrador TIC, Welcome to Atlassian Community! Automation cannot change the issue type, it can only change the request type. So you would have to make a new incident request type that is using the petition issue type in order to do this. 

Hi @Jochen Daum, Welcome to Atlassian Community! The video that you found only applies to team-managed projects, is that what you are using? The other option to add existing issues to an epic is to go to the backlog and drag the issue over to the corresponding epic. 

Hi @Ash Scott, Welcome to Atlassian Community! Are you using a team-managed project or company-managed project? Does all your users that do not see the boards have a Jira Software license assigned to them? 

You have two options, the first one is to create a new transition that either sets the resolution as part of the post function or have a screen with the resolution field on it. The second option is to use automation to set the resolution, just create a scheduled rule that select these three issues and then set the…

The short answer is no, you cannot automate adding new quick filters. There is not API endpoint that allows you to do this.

@ABD You should be able to get the name by using {{sprint.name}}, and you can learn more about the logic of the syntax I provided if you check out the link in my post above.

You have to use the account that is associated with your instance. 99% if the endpoints in Jira require an API token, exceptions are some JSM endpoints.

Hi @Laura, Welcome to Atlassian Community! You can create an API key if you go to id.atlassian.com. Under security you can create and manage your keys.

Hi @Mayank Gupta, Welcome to Atlassian Community! The log indicate that someone changed the name of the Done status to Cancelled. If you are a Jira admin you have the permissions to rename statuses, but you need to be very careful since a rename will affect all workflows using that status.