Mikael Sandberg Community Champion

Yes, that is possible. You can use math expressions to sum up the values for the four fields and then use if/else conditions to set the sum risk.

Hi @Gabriela-Rodica Stroe, Welcome to Atlassian Community! No, the parent link is a single select field, so you cannot set more than one parent. 

Hi @DC Hall, Welcome to Atlassian Community! In order to rename a workflow you have to make a copy of the existing one and then rename it. Go to Settings > Issues > Workflows and locate the workflow you want to rename. 

No, wildcard searches is only available for text fields, like summary and description. You would need an app that extends JQL in order to do fuzzy searches on dropdown fields. If you look in the Marketplace you will find apps that can do this.

Currently that is not possible, Analytics does not have a download feature, nor does it have a public REST API.

You should be able to use [field name] = "1.0 (Unsupported)", or if you are searching on multiple values [field name] in ("1.0 (Unsupported)", "1.1 (Unsupported)")

You can create a separate queue just for the sub-tasks and then in your other queue just update the filter to exclude subtasks by adding this to it: issuetype != Sub-task

Yes, it is possible. Go to project settings > request types and select the type you want to change. Under the request form you can change the order, and add/remove fields. See this KB for more information.

Hi @Pratip Kumar, Welcome to Atlassian Community! You would need an app that extends JQL in order to do that. I know Enhanced Search/Scriptrunner and JQL Tricks can do this, but there are other apps in the Marketplace that can do it too.

When you update a workflow it will not automatically update boards associated with the project. You have to manually go to board settings > Columns and map statuses to the correct columns.

If you go to admin.atlassian.com > Product > select your site on the left that will take you to your users. From here you can search the user and click on their profile and you will see what they have access to: The next thing I would check is in the project that the user has been assigned the role Service Desk Team.

Have a look at this blog post, it could be that the main branch is missing in the repo.

Hi @Le Ann Langston, Welcome to Atlassian Community! Make sure the user has been assigned a JSM license. Based on your screenshots the user have Jira access but has not been assigned JSM access. Go to admin.atlassian.com and lookup the user to enable them as an agent. 

@Blake Peavy The way I did it in the past when working with Git was to start fresh and ignore the history. You could still keep the original repository around if there is a need to see the history, but in 99% of the cases no one ever needed to see the history.

Are you running this from the git bash command line or Windows cmd? If you are doing it from cmd then you need to replace all ' with ", because Windows only recognize ".

Hi @Olufemi Ode PMP Welcome to Atlassian Community! If you are referring to Scrum/Kanban boards then the answer is no, those boards can only have one filter associated with them. But you could include multiple projects in that filter. If you are referring to Plans (Advanced roadmap), then the answer is yes. 

Currently that is not possible, but Atlassian is working on adding project-level permissions and is currently on track to be released in Q1 2023 according to the public roadmap.

Hi @Allen Huffman, Welcome to Atlassian Community! Have a look at this KB, it outlines the steps that you need to do to refactor your repository into smaller ones. Basically what you do is create a new repository, clone the existing one into it, remove the link to the original one, remove everything that you do not want in…

When you link a Jira field to your field in Forms it will replace all the options based on what the Jira field has, hence why you are seeing the options for "Select login or...". If you remove the link to the component field you will be able to set your own choices.

No, you would have to use an app in order to do that.

Hi @srinivas yeswanth, Welcome to Atlassian Community! You would need an app in order to do it and a quick search in the Marketplace shows that you have a couple of options.

In that case you could use math expression with a smart value to get the number of days that should be added to the due date. Something like this: And then use that as part of the smart value to set the due date like this: {{now.plusDays({{days}}).jiraDate}}

Yes, those at the two ways of creating the object type. If you click on Object schema > Configure and go to the Roles tab, do you have groups added to the role Object Schema Developers? 

Hi @Andrew King, Welcome to Atlassian Community! After you created the schema in Assets, did you also create an object type? The object type defines the attributes that you can set on an object and has to be created first before you can create the actual object. 

(Correcting myself) You could try WAS NOT as part of your JQL like this: project = PD AND status = Development AND "Development Start" >= -7d AND status WAS NOT Development That should exclude issues that have already been in the Development status. Another option is to have a post function on the circular transition that…

No, a workflow can only have one create transition. Instead of using fields and automations your other option would be to use different workflows for each issue type.

That is the preferred one, otherwise you would have to add each person in your org manually.

No, the customer do not have to reply to the email to be added. You could add your internal users if you like, and the easiest way to do that is if you have a group that they all belongs to. That is I added my org as customers for out ITSM project. Just add the group with the role of service desk customer.

Just change the x in the smart value to the number of days you want to set the due date to, for example {{now.plusDays(5).jiraDate}} if story point is 1.

Yes that is possible and fairly simple to do. All you need to do is trigger on the transition to In progress, check if story points exists and if so use the if/else condition to set the due date using this smart value {{now.plusDays(x).jiraDate}}.