Mikael Sandberg Community Champion

JQL can search on history using was or changed, but that is limited to just a subset of standard fields like status and resolution, it cannot search on history for custom fields. Based on the documentation for EazyBI you can report on the history for custom fields, see Import issue change history. I am not sure if you are…

Do you know the size of lookupIssues? I would add a log action to see what {{lookupIssues.size}} returns. 

Hi @Jaina Mistry, Welcome to Atlassian Community! What you have above is an incomplete math calculation, they usually look something like this: {{#=}}{{issue.Invoice Amount}} * 1.2{{/}} But instead of using calculation on the due date you could use lookup issues and then use the JQL due = -5d and then check the size on…

Hi @Brian Abrams, Welcome to Atlassian Community! A couple of things to check if you are using a company-managed project, has resolution been added to to the create screen? Is there an automation that is setting the resolution on issue create? Check your workflow to see if there is a post function that is setting the…

You are using the wrong domain, it should be the instance URL, not api.atlassian.com. Your URL should look something like this: https://my-instance.atlassian.net/wiki/api/v2/spaces 

The order you need to delete this is delete the issue type screen scheme first, then the screen theme followed by the screen. Here is a good reference on how the different schemes are connected, the KB is for Data Center but it works the same way on Cloud. Basically you start with the scheme closed to the project and work…

Hi @John Funk, So it only work if you have a single dependency specified. I you have multiple it will pick it based on the alphabetical order as you discovered.

Yes, try and add them, at least temporarily, to the modify reporter permission, just to see if that makes a difference.

Did the detailed log show any errors? Does the users have access to the project?

And I would recommend that you check the box for Map field value, it will then tell you if the user is being correctly mapped for the first line in the csv.

Are you mapping the the field when doing the import?

You could do that by converting {{now}} to long date in a smart value and then use if/else branches to see which month it is and create the tasks in the specific project for that month like this: The other option would be to have separate automations, one for each month that runs yearly and create the tasks that way.

Hi @Melissa Perez, Welcome to Atlassian Community! The way we do onboarding is that we have the main request with all the details, and when are then using either tasks or subtasks (tasks are created in other projects so that those teams do not have to access multiple projects). Another option since you have a lot of steps…

Yes, you can get the date by going to the history tab in the issue and then look at when the change happened. There are also a couple of apps in the Marketplace that can make this a bit simpler.

You can set it to run on a monthly basis like this:

Hi @Daniel Zarate, Welcome to Atlassian Community! No, Advanced Roadmap is not part of JWM Premium, that is only included in Jira Software Premium plan and above. But if you have JSW you will also have access to JWM, as announced here.

Hi @David Mallette, Welcome to Atlassian Community! Secret keys are Data Center only, and I did a quick search and could not find a suggestion in jac to have this added in Cloud. I would recommend that you add one under Automations for Atlassian to consider.

Just to add to @Rebekka Heilmann _viadee_ answer, here is a good reference to see how all the schemes are linked together. The KB is for Data Center, but it works the same on Cloud.

The short answer is no, filters do not have "global variables". The workaround would be to use something like Custom Charts and the simple search gadget which can control other Custom Charts gadgets on the dashboard. There are other apps in the Marketplace that could do this as well.

Make sure that you have checked "Allow rule trigger" under rule details on the second automation that runs on issue linked.

I would start by looking at the workflow and the status that has the approval process on it. Is the approved transition going directly to the closed status? Without knowing what the workflow looks like it is just an educated guess. 

You can get it by either go to Teams and lookup the user, the account Id is the last part of the URL for their profile. You can also go to admin.atlassian.com > Product > Users and search for the user there.

JSM now has Forms (formerly ProForma Forms) which allows you to set up a dynamic form that has its own URL. But in order to access it users have to have access to your instance. You can learn more about Forms here.

Yes, that is possible, but the user has to exist on your instance and you have to use their email address. You can find more information about how to prepare your csv file here.

The difference is that customers added from within the project (your first screenshot) are added as portal-only customers. Some time ago Atlassian introduced external users, and they are added as users and you will see them in the users list in admin.atlassian.com. These external users can be managed by setting customer…

Hi @KP, Welcome to Atlassian Community! Yes, that is possible. What you need is a scheduled automation that checks if the review date is 90 days out, and if so then transition the issue. Here is an example, this is a rule I have that checks the due date and if it is 90 days out it adds a comment to the issue.

Okay, so check if there is a transition in the workflow that will take you to the Approved status from the initial one. If you do not have a global transition to Approved that would explain the error. You would then have to either follow the workflow or add a global transition. The global transition can be hidden by adding…

Are you running the rule as Automation for Jira or another user? Check that you can transition from the current status to Approved.

You can try and add the label in the automation that clones the issue by using the branch "Most recently created issue".

In that case add your domain under User access settings if it not already there and give them JSM customer access, that is how I have it set up for our instance.