Mikael Sandberg Community Champion

Correct, and customers can either add themself or an agent can do it. It all depends on if you are allowing it or not. You configure that from Settings > Products > Customer access.

There is an API endpoint to get pull requests, but it works on the repository level. So you would have to combine that with getting all the repositories associated with a project and then loop over each repository to get the pull requests.

Yes, anyone can be added as request participants, and it can either be done by the customer via the portal or by the agent from the issue view. And adding a participant has no affect on the license, it is only agents that needs to have a license, customers are free.

Hi @Kathryn Moore, Welcome to Atlassian Community! Change the smart value for lookup issues to {{lookupIssues.size}} because smart values are case sensitive.

Okay in that case you would have to use OR in you query, something like this: project = xxx AND (status = open OR (status = closed AND resolutiondate >= startOfWeek(-1))) This query will search project xxx for all issues that are open OR issues that are in the closed status and had the resolution set since last week until…

Hi @Simranjit Singh, Welcome to Atlassian Community! JQL is short for Jira Query Language and is used to filter out issues either within a single project or multiple projects. Have a look at this free lesson about JQL.

The query that you have is correct, it will give you all issues in the specified project, that are in the specified statuses and was created on or after start of last week. You can actually remove the w since that is implied by the function. Note that start of week is Sunday, and end of week is Saturday.

@Michael Ballenger The picture you included is from Advanced Roadmaps Guide and looks to be from a DC instance. The numbering has nothing to do with the ordering, the list is read from top to bottom in Advanced Roadmap. And you are right, this hierarchy is only working if you have access to Advanced Roadmap. Here is a…

Here is an example from an import that I have that updates asset objects twice a day: 2022-11-09T22:05:01+00:00

Assets expect the format of the date to look like this: YYYY-MM-DDTHH:mm:ssZ And it should be in UTC time zone.

Hi @Ismael Garcia, If you have enabled the wiki style renderer in a paragraphed field you should see the same controls as in the Description field: That indicate that the paragraph field is wiki enabled and should support the text formatting notation as well. 

So the web request allows you to make a REST API call, in this case that would be to go the issue which includes the approvers and their decision. You could then use that to figure out the how many have approved the request. Your other option would be to update a field every time someone approves and compare that number to…

You could do that with automation. What you would have to do is update the workflow so that approve/decline is not automatically changing the status based on the decision. Then have the automation trigger on Approval completed that checks via web request to see if you have majority approval, and if so transition the…

Hi @Jack Charnley, Welcome to Atlassian Community! You can hide all the SLA fields if you go to Project settings > Request types and click on one. From here if you go to the issue view you will see SLAs under the context view. Drag it to the right and it will be hidden for that request type. If you want to remove just Time…

Your other option is to trigger the automation when work is logged on a request.

Hi @Jack Charnley, Welcome to Atlassian Community! There is nothing in log work that would allow you to do this, but you could do it via a scheduled automation, and have it add an internal note to the request once you get close to the estimated time. You just have to look at {{issue.timetracking.remainingestimate}} and if…

Yes, this can be done with automation. If you create a scheduled automation you can search for specific issues, and lets say that the due date is 90 days out then send a message to the assignee or add a comment to the request that something needs to be done. If you look in the Automation library, (Project settings >…

Hi Kate, Welcome to Atlassian Community! You set up the hierarchy if you go to Plans > Setting > Advanced Roadmaps hierarchy configuration. Note that the hierarchy applies to the whole instance, there is no way of setting it for just one project or have multiple different ones.

You should use an API token instead of a password. If you do not have a token already, go to https://id.atlassian.com/manage-profile/profile-and-visibility and from there go to security and generate one. It is recommended that you base64 it once you have gotten it to work.

That means that the authentication isn't working. Try using 'Authorization: Basic <user_email:api_token>' instead of Bearer to see if that works. 

When you are searching and trying to exclude labels (and components) you also have to account for issues that do not have a label at all. So try this: (labels != Backlog OR labels is EMPTY) AND status in ("Awaiting CAB approval", "Awaiting implementation", Escalated, Implementing, "In Progress", Open, "Peer review / change…

Hi @Luiz SSO PUBLIC, Welcome to Atlassian Community! The user that you are using the the authentication when sending the end point has to be part of one of the groups that you have given global Jira permissions to. Your header in the call needs to include 'Authorization: Bearer <access_token>' or 'Authorization: Basic…

Hi @Gabriel Mercer, Welcome to Atlassian Community! JSM out-of-the-box does not allow you to have multiple portals with unique URLs, you would need Refined for Jira in order to do that. 

Correct, you need the Slack ID for the user you want to message. If you implement the scripts mentioned in article I linked to above you can send the Slack message to anyone, including the reporter. What you would do in the automation is to use the web request to get the user property for the reporter to get their Slack ID.

Hi @EvaNali Spacek, Welcome to Atlassian Community! Do you have child object types already created? The inheritance can only be enabled on an object type that don't have any child objects.

Make sure that the filter that is used by the board is picking up the issue that was moved. If you to board settings > general you can see the filter that is being used by the board.

To add to @Ashley Hudson answer, the colors you see in Insights is based on the status category that you have assigned your statuses to. Gray is todo, blue is in progress, and green is done. So if your status to do is assigned the category in progress that would explain why Insights is showing those issues as in progress.

No, you cannot prompt for input via an automation.

Issue security is not a Cloud only feature, you can set it up on Server/Data Center as well. The set up is the same, you just create a security scheme, change your permission scheme, add the security level field to the screen and then set it on the issues that you want to limit access to. Have a look at this KB for more…

Hi @Michael Lukay, Welcome to Atlassian Community! It can be done using automation and REST API. It all depends on what you are using for your email distribution. We are currently not doing this but because we use Okta it would very simple to use an automation that triggers an Okta Workflow that adds/removes a user from…