Mikael Sandberg Community Champion

Hi @Daniel Martinez, Welcome to Atlassian Community! Check your workflow to see it the resolution is either set when moving to the current status, or if you are allowing issues to move between any status, make sure that the resolution is cleared if you for example move from Done to Open. 

Hi DB, Without an app you can only add a header image to your pages like this: Anything else require an app like Scroll Viewport, Refined, or any of the other Theme apps that you can find in the Marketplace.

Here is what I would do, after the lookup issue component, add a log action component and check the size of lookupIssue by adding this to the log action: Size: {{lookupIssues.size}}

Yes, you can include the URL to the issue, something like this should do it: {{#lookupIssues}} * [{{key}}|{{issue.url}}] {{issue.summary}} {{/}} I think the reason you are having issues with the lookupIssue is because there is no .name field.

Hi @Matt Baum, Welcome to Atlassian Community! You should be able to do this using smart values, here is a link to the ones related to the sprint and you should be able to get the list of issues by doing an issue lookup to get the issues in the sprint and then use the list option for smart values.

Hi @nitin rathore, Welcome to Atlassian Community! Just go to Project settings > Permissions and click on Actions > Use a different scheme and then follow the on screen instructions.

You would either have to use Advanced roadmaps, it can give you a view like that. Your other option is to use an app like JXL, Structure, Swanly, or any of the other apps in the Marketplace that can do this.

Hi @Enguerrand de Pompignan, Welcome to Atlassian Community! Without an app that extends JQL you cannot create a query that will return the result you are looking for. You would need Scriptrunner, JQL Tricks, or any of the other apps in the Marketplace that extends JQL. 

@Elena Dzhordzhilova This should be a separate question. Based on the documentation for Bitbucket you can only get the email address for the current user, there is no way of getting the email address for other users, at least not at the moment. For Jira and Confluence you can get the email by accessing the Get user…

Hi @[deleted] Welcome to Atlassian Community! What you see is expected and part of Atlassian's privacy commitment and how user data is handled. You can learn more about the changes here, Changes to usernames in Jira Cloud.

On the Epic branch, change the condition that checks the status, because the way you have it configured right now the epic would have to be status = In Progress in order to transition it to In Progress.

Something like this should do the trick: In this case I have added a condition to only look for Stories or Tasks that are transitioning, and then transition the epic only if it is on the To Do status. Because you want to move the epic when the first story/task is transitioned there is not need to check that stories/tasks…

The example I posted above should only transition the epic if all stories/tasks in it are in the done/completed status, that is what the second condition in the epic branch is checking, the "And: Stories (or other issues in this Epic)" part. The video that you found is indeed showing the inverse when the epic is moved to…

No, if you create it from scratch you should be good. If you still have an issue with the trigger not running and the audit log is saying "no actions performed" then you should start there. You could add a log action after the initial trigger to see if it gets to that component.

Okay, so try this. On the initial trigger component try and change the status it triggers on, I have noticed that if you use a rule from the library you have to change the default settings for the automation to trigger correctly. 

Your JQL is missing status = "In progress", using just = "In progress" is not a valid JQL. When you did the test, did you move a story/task to completed or an epic?

If you go to Project settings > Automation and look under Library there is a rule called "When all stories are completed → then close epic" that you can use as a starting point, just change the statuses to fit both of your use cases.

Yes, Assets can be used for ITAM, that is the most common use for it. That is what we use it for, among other things. You have a couple of options to sync InTune to Assets. There is this app in the Marketplace that can do it for you, Microsoft Intune Importer, or you could do it using the REST API, that is the solution we…

Hi @Phillip Jones, Welcome to Atlassian Community! On, you cannot "lock" the issue security scheme so only a subset of Jira admins can modify it. Once you have Jira admin permissions you can make changes to it. Atlassian is working on a more granular permission scheme so that might be something that will be available in…

Is the request type the last one you created? Automation does sometimes have an issue seeing that last created request type, you could create a new one or use a JQL condition instead which would look something like this: "Request Type" = "My request type"

Hi @Dadapeer P B, Welcome to Atlassian Community! You need to check your workflow, based on the error message you have validators on the transition to Build status that makes those fields required. So you could either remove those validators, or add the fields to the screen used for New Feature. 

Hi @Ismael A. Justiniano, Welcome to Atlassian Community! You can do this with automation, all you would need is one that checks when the request is created what request type it is and if it is, lets say, external then send an email with all the information to your msp, and then delete the request. Something like this…

I'm interested, we have a dedicated space in Confluence that we use as an intranet.

Also, I would remove .data.key and only use {{issue.customfield_12524}} to see if that makes a difference.

I would recommend that you add a Log action component after you create the smart value to verify that {{parentLink}} has the right value and then go from there. Based on the audit log I am guessing that {{parentLink}} might be an empty value.

My bad, you need to add Time tracking to the screen, that will add the original estimate field.

Hi @aaron.kjosa, Welcome to Atlassian Community! You should be able to change the fix version via bulk edit, it should be the second option when you do it: Just make sure that Fix version has been added to your edit screen. 

All you have to do is add Original estimate to your create screen. Just go to Project settings > Screens, select the screen used by the issue type you want to change and then add the field to the Create screen.

The half hour steps is just the default ones, you can always manually enter the exact time like this:

Here is an example from my sandbox: