Mikael Sandberg Community Champion

No, it is not possible to use the name instead of the sprint Id. The reason is that the sprint name isn't unique in your instance, you could have two or more sprints with the same name.

Yes, that is normal behavior if you are using project roles/groups to limit the access. When you do that then you have to add user to the right roles under people. The default permission scheme is basically set up so if you have access to the product then you have access to any projects. I always recommend using project…

Adding a group in the permission scheme does not automatically add them to the project. Here is a good overview of how Jira permissions work. If you look at that default permission scheme it allows anyone with application access to browse project and in that case you would not have to add them under People. But if you…

Correct!

The only permission needed to use that endpoint is browse project permission, so the question is what permissions do you have in the JWM project? Can you access the project from within Jira? If so then the endpoint should return all issues. 

Then you need to check what permission you have, I just ran it in my sandbox against a JWM project and all the issues were returned. this is the query I used: /rest/api/3/search?jql=project%20%3D%20JWM

Hi @Dev Bonebone, Welcome to Atlassian Community! The Search for issues using JQL endpoint can get all the issues for a specific project.

Hi @Evonne Fernandes, Welcome to Atlassian Community! The only thing that controls idle session duration on the Atlassian side would be if you have an authentication policy set that have a duration set to shorter than the default 30 days. Are you using an identity provider like Okta to get access to Jira? Does this happen…

In order for the customer to see a requests in the portal you have to set the request type field. This field controls if the issue will be visible on the portal or not. Unfortunately you cannot create a request type that is associated with a sub-task since sub-tasks have to have a parent issue. So in your case you would…

Hi @elyse, Welcome to Atlassian Community! Customers can always go to the portal and view all the requests that they have submitted or are request participants on by clicking on Requests > All From here you can select to see open and closed requests. 

As I have stated above, you cannot do that in a JSM project. It can only be done if you have access to Jira Software, and if so then you can create a Jira Software project and then create a board in there and change the filter for that board so it brings in the requests from your JSM project. But if you do not have access…

I am not sure that I follow, are you trying to integrate an third-party application with Jira? If so the recommended way is to use apps that you find in the Marketplace, or create your own. The App links cannot have admin rights on the Atlassian side.

No, in JSM Cloud you can create a simplified Kanban board, not a Scrum board. 

Hi Jane, Welcome to Atlassian Community! The short answer is no, you cannot give admin access to specific application links. In order to get to the application links you need Jira admin permissions.

The only way if you want to use sprints is to set up a Jira Software project and create a scrum board there. Scrum and sprints are JSW specific features.

Hi @tyler mikkelson, Welcome to Atlassian Community! The way you have is set up the check to see if the comment is internal is only happening on the IF branch. If you look in the template you will a rule called "When a comment is added → update the status" that looks like this: As you can see this one is checking if the…

Hi @Dipen, Welcome to Atlassian Community! The card color is a company-managed project only feature, there is nothing similar in team-managed projects.

Have you tried using the regular expression validator? I have one that hides the In Progress transition if the Triage field is set to Untriaged like this:

It should be pretty straightforward, I expanded my test from above so that it will add the input to the description. Here is what it looks like when I run it: And this what it looks like after And this is what the edit issue field looks like:

How do you populate the field value?

Hi @Caressa, Welcome to Atlassian Community! The input prompt is unrelated to any fields on your issue, but you could use the value that user puts in as a value for a field on it. Looking at your screenshots it looks like you overcomplicated the manual trigger. Here is an example of a rule I just created: I suspect that it…

Just a thought, but instead of using email to Slack, why not use the emailed request? Each JSM project can have an email address that can be used to create requests. All you would have to do is instead of forward the email to Slack, just forward it to JSM. 

If you could upload a screenshot of what the rule looks like and the audit log that would help troubleshoot this. Without that information there could be anything that is causing it. A generic recommendation would be to add an audit log component before the rule fails, it could show the value of a smart value or a field.

Hi @Krystle Webster - IPOM, Welcome to Atlassian Community! The minimum license tier for JSM DC is 50 agents, and for Confluence DC the minimum is 500 users.

You cannot set a default reporter, it will aways be set to the person that clicked the create button by default. You can manually change that when creating the issue, or have an automation that changes it after the issue has been created.

Hi @Nyree Adams, Welcome to Atlassian Community! You will have a much better success getting this solved if you contact Beeline support or someone at your company. You ended up on this community because Beeline is using Atlassian products.

Doing a quick search in the Marketplace it looks like there is only one app that can do this, Jira Boards.

If you go to you email log you will see that it says that the user is pending verification. The external account type has existed for a while, but recently users had to start verify their accounts before they can submit requests. This the reason I am not using External account types. The difference is that if you do not…

Hi @Montie Steele, Welcome to Atlassian Community! So if I understand this correctly you have two automations, the first one creates the cloned issue and lives in project 1, and a second automation that does the transition that lives in project 2, correct? If that is the case, make sure that the second automation has the…

Hi @Centro de Excelecia TI, Welcome to Atlassian Community! One option instead of using custom fields and automation would be to use SLAs instead. They will show the amount of time it took for the SLA to stop based on the configuration.