Mikael Sandberg Community Champion

@Faruk Erdem This should probably be it's own question that reference this one. Those bubbles are based on the assignee and cannot be changed to also include other user picker fields.

It's because of your branch, anything within it will run on the issue(s) returned by the JQL and not the issue that triggered the automation. Instead of using the JQL branch, have you tried using the lookup issues action and then check the size returned?

There is, you can find all the smart values here, https://support.atlassian.com/cloud-automation/docs/smart-values-in-jira-automation/

Great topic @Jimmy Seddon! Yes, I do have too many subscriptions, and should probably do an inventory and think about if we really need some of them or not. But I can already hear my two daughters protesting if we do. But I did get rid of the Roblox subscriptions without any objections, so who knows. There are a couple…

Yes, that looks correct.

Yes and no. You can set up the rule to trigger on when the field is changed and then check and see if {{initiator}} is in the specific group. But you cannot use a one-time rule to get the history of the issue to see if the user made the change.

It would look something like this:

So you do not see the cog wheel up in the right-hand corner?

You need to be space admin in order to export the space and have the export permission, being site and org admin does not guarantee that you have that permission. If you are not space admin you can always change that from Settings > Space permissions. 

Are you trying to export a single page to XML or the whole space? The XML option is only available if you go to Space settings > Export space.

Okay, unfortunately currentUser() is not supported in AQL, at least not yet. The only thing I can suggest is that you submit a suggestion to have that added. Go to jira.atlassian.com to log it. 

Correct, you will have to use the create a variable multiple times, but as long as you use the same name it will just update the value for the variable.

The automation would look something like this:

If you create the automation to trigger on sprint started then that would also update the due date for issues that are moved over from one sprint to the other.

My teammate is also not on the Community, but Carley McGee was instrumental when we onboarded JSM two years ago and got all of our business teams interested in using it. 

It depends on if you are using forms on your request form or not. Is you are only using the request form it is currently not possible unless you have an app that allows it. Actions for Jira Service Management is an app that was submitted to Codegeist 22 that allows you to edit fields after the request is submitted. If you…

@Derek F You can set the variable to null outside of the if/else block and then use it within to set it to the right value.

@Kelly Arrey yes, if you create the variable outside of the if/else block it becomes a global variable and can then be used inside the if/else block. Have a look at the article above that Derek linked to.

If you set the due date when the sprint is started then you would not need to adjust it if an issue is move to a different sprint. The only exception to this would be if you move the issue to another open sprint. Correct, you would need to know the sprint Id for each sprint, so in order to automate it you would have to use…

Sorry, missed the part about Jira access. The above only works for users that have Jira access at the moment, but hopefully that will change in the future.

You would need Refined in order to do it for projects that are not a JSM one. Out-of-the-box it is only JSM projects that have a portal.

I have two options that you could use, the first one would be to have two automations. The first one would trigger on when the sprint starts and it would set the due dates on all issues associated with that sprint. The second automation would then be based on the article you found. The second one would use REST API calls…

Yes, that is possible. All you have to do is go to the Roadmap view, click on Share and copy the URL and then past the URL directly onto the Confluence page (don't use the link macro) and that will add the view similar to this:

Hi @Travis Anthony Wolf, Welcome to Atlassian Community! Instead of using the User profile, use the Profile picture macro. That will just add the picture and if you click on it it will forward you to the profile page. 

Hi @Anil, Welcome to Atlassian Community! Have a look at this question, you can add the following to the announcement banner and it would be project specific: <p style="display: none;" id="demo">Sample Announcement</p> <script> if (window.location.href.indexOf("projects/SP") != -1) { document.getElementById("demo").style =…

It depends on where you create the variable. If you look in the article they are creating the variable first before using it in the branch. If the variable is created with the branch, you will not be able to access it outside of that branch, that's the difference.

Hi @Ryan McGee, Welcome to Atlassian Community! Yes, that is possible and the automation would look similar to this one that is in the automation library:

Is the log action within the if/else block or outside? The screenshots indicate that it is outside of the if/else block and that would explain why the variable is null. A smart value that is created with a if/else block is only available within that block and cannot be accessed outside of it.

Hi @sai prakash, Welcome to Atlassian Community! In order to change the commit comment you have to use the git amend command. Please see this article for more information on how to do it. 

Hi @Alicia Simon, Welcome to Atlassian Community! Try this JQL and see if it works: status = Done AND updated < -5d