Mikael Sandberg Community Champion

Hi @Michael Gomeau, Welcome to Atlassian Community! I assume you are using a team-managed project since you are seeing rules which is in the new workflow editor that currently only is available in a team-managed project. Anyways, team-managed projects do not allow you to add a transition screen, that is only available in…

When you are setting the sprint for the crated task are you using smart values or the Active sprint option? The smart value {{sprint.id}} should get you the Id of the sprint that triggered the automation.

No, the Atlassian Id is not always 25 characters, it can be up to 128 characters. You should use the find users rest end point to get the Atlassian Id instead of relying on substrings.

Hi @Noel Martinez, Welcome to Atlassian Community! Currently it is not possible to make the project category required. I checked jira.atlassian.com and could not find a suggestion to add that feature, so you could create one for Atlassian to consider in the future. 

Hi Tina, Are you tracking these serial numbers in Assets? You should be able to create the company serial number by using smart values and combine the two different ones, something like this should do it: {{sic}}-{{dell}}

Hi @Suleymanova Shabnam, Welcome to Atlassian Community! In order to add custom fields to your requests you have to add it to the screen used by the issue type. Go to project settings > issue types and click on the screen scheme for the issue type that is associated with your request type. From here you can add fields to…

In order to create a nested JQL query to get the result you are looking for you would need to get an app that extends JQL, default JQL cannot do that. There are several apps in the Marketplace that can do this, I have used Scriptrunner/Extended search and JQL Tricks in the past to do this.

Teams in the Responders field is referencing teams that you have set up in Opsgenie, not the teams that you have created under People. When adding someone to that field it will create alerts based on rules that you have defined in Opsgenie. You can learn more about it here.

Is sounds that you either have Refined to set up your portal or you are using external resources link to add your JSW project to the portal. As you mentioned JSW does not have any portal settings.

Hi @[deleted], Welcome to Atlassian Community! Portal groups cannot be assigned to customers, portal groups are used to group your different request types to make it easier to find the right form. You can add/edit/remove groups if you go to Project settings > Portal settings > Portal groups. 

Hi @Alan Danish, Welcome to Atlassian Community! You can find the Sourcetree enterprise installer here, https://www.sourcetreeapp.com/enterprise 

You have a couple of options here, you could add the links as part of the instructions so the link is shown at the top of the request like this: Or you could use Forms instead and in that form have a section with the links. Your third option would be use Message custom field (for edit).

Hi @Muut, I looked at your post and moved it out of the spam filter. Sometimes the filter can trigger on included links and that is what it looks like happened in this case. 

You can use the Message custom field to do this. In order to view the message in a transition screen use the Message custom field (for edit). You will see both of these custom fields if you go to Settings > Issues > Custom fields and click Create custom field > Advanced.

In order to edit a field in an automation it has to be available on the screen and cannot be hidden. So make sure that the field is on the screen used by the issue type and that it is not hidden.

Hi @Katrien Reynaert, Welcome to Atlassian Community! JQL doesn't allow you get get a list like the one you are looking for. You would need an app that allows you to view/search the history in order to do it. If you search for history in the Marketplace you will see apps that can do this. 

Hi @Chaitanya CJ Patel, Welcome to Atlassian Community! Advanced Roadmaps has a limit of 5000 issues in a single plan, so if you exceed that it is recommended to spread the work across multiple plans. Please have a look at this KB for more information.

So it depends on what type of project you are using, for example the screenshot you included above is showing the backlog from a team-managed project which behaves a little bit different from a company-managed project. You will also see differences in functions based on the project template, some features are only…

I would create all tasks within the same automation. Yes, there is a limit on how many components you can have, currently that is 65. So you could brake it up in two rules and either have both trigger on when the epic is created or use a dispatcher rule that is calling each of the two rules via web requests. You can learn…

Yes, Insight is now known as Assets, and here is the announcement about the name change earlier this year, https://community.atlassian.com/t5/Jira-Service-Management-articles/Coming-Soon-Insight-Changing-to-Assets/ba-p/2068056

Note that issue security does not hide projects, but you can use that together with permission schemes to hide issues within a project.

Hi @Caue Fajoli, Welcome to Atlassian Community! You do this by creating a new permission scheme that you apply to all your existing project and then I would recommend that you allow users to browse the project and edit issues based on project role instead of the group. You can then control who have access to a project on…

That would be {{issue.updated}}

The resolution field will become required if you add it to a screen and then associate that screen with the transition that takes the issue to the closed status.

Hi Maggie, The smart value that you are looking for is {{initiator.displayName}}, that will give you the name of the use that triggered the automation.

You would need an app to do that, like Behaviours - Scriptrunner or Power Scripts. Both of these can control what is visible in a field.

You can do this using automation, and have it trigger on when the sprint field is updated. Something like this should do it: Note that this example is very simplified and you may want to add a condition that checks who triggered the change to the field so that the release manager don't get notified for all issues added to…

If you do not have an app that extends JQL, your only option is to add each task issue key to the query like this: issue in linkedIssues (JRA-123, JRA-456, JRA-789)

The "include current status" means that it also takes into affect the current status the issue is in, so you want to check that so issues that is currently in the Rejected status cannot transition out of it. Example, if the issue is currently in Rejected and you have not checked "include current status", you will be able…

Hi @Rocio Lechuga, Welcome to Atlassian Community! It can be done by using automation, something like this would do it: Note that this is a very simplified rule and would trigger on all issues created in the project, so you would want to add more conditions to it. You read more about Automation here.