Mikael Sandberg Community Champion

Is the new project the Online Technical Support? Your screen is shared with 4 project, but the field context is limiting the field to only Online Technical Support...

Is that field on the close screen? If is on the screen, check your field configuration to make sure that the field is not hidden. Also check the field context to make sure that it is set to global and not just to a specific project and/or issue type.

Go to the workflow you want to edit, and click Edit workflow. In the new editor, select the transition you want to add the screen to and then click add rule on the right. If you are using the old workflow editor, click on the transition and then click on Edit on the right-hand side. That will bring up the edit transition…

No, the status would still have the approval step on it, and then you use the automation that add the users that should approve based on the cost.

If you do not want the user to select the resolution then remove the resolution field from any screens that the user have access to and then add a post function that sets it. Here is an example of what it looks like in both the old and the new workflow editor.

If you are using the new workflow editor you associate the transition with a screen by adding a new rule and then select the screen. It is grayed out in the screenshot because the transition already had that rule.

Are you using a company-managed project or a team-managed project? @Abdallah Khaled is correct that if you are using the old workflow editor you cannot add new transitions to a workflow if it is active. But this has been fixed in the new workflow editor. Back to what you listed in your question above, you cannot add a…

@Shannon Hoskins As I mentioned above, you need to associate the new workflow with the workflow scheme that the project is using. Please follow the the instructions listed above by me and @Joseph Chung Yin If you do not see Project settings in teh project you need to contact your project admin and have them do this change.

Hi @Shannon Hoskins, Welcome to Atlassian Community! Assuming this is a company-managed project (you can't copy team-managed project workflows), once you copied the workflow you have to associated it with the workflow scheme that the project is using. You can do this by going to Project settings > Request management >…

You could do this based on a single approval status too. In that case the automation would figure out who should be added as approvers based on the cost, and then the approval step would have "all approvers need to approve" before the workflow moves the item to the next status.

Yes, it is possible and you would do this using automation. Your workflow would have all approval statuses, and you can then use automation to bypass approval status based on the cost. I created a similar approval workflow for our HR project for promotions and transfers. Based on what information not all 4 groups needed to…

Hi @Alexander Pisarewski, Welcome to Atlassian Community! I would start by looking at the free learning paths that Atlassian University is offering. They also offer live training. Another option is to work with an Atlassian partner on getting custom training if needed.

Yes, that is possible, you would just have multiple transitions to the specific Done status or make it so the destination status allow all statuses to transition to this one. But I would question why you need multiple Done statuses, will you filter on these later on? Or would using the Resolution field work instead?

Looking at the attached screenshot you are not selecting the resolution, the field Final Resolution is just a custom field and not associated with Resolution. The resolution field is a single-select dropdown field and would be marked with a red asterisk indicating that it is required. So you should check your workflow for…

As outlined in the KB, you should never use Unresolved/None as a resolution. And if you get a screen and select the resolution and it is still set to Unresolved after that then you most likely have a post function on the workflow that sets it. Post functions will aways overrule anything that you select on a screen. Yes,…

You do not have to use another smart value, all you would have to do use something like this to set the Project Name field for example: {{issue.summary.substringAfter("Project Name")}} This of course assume that the summary only have the project name as a sub string in the summary. If you need to extract multiple values…

Hi @Jon Ripperdan, Welcome to Atlassian Community! The default page is based on a blueprint that is based on the template you selected for your space. You can modify these blueprints if you go to Settings > Global templates and blueprints. You can read more about it in this KB. 

Jira does not have such a feature out-of-the-box when creating new work items. There apps in the Marketplace that can detect duplicate/similar items after they have been created, or you can create an automation that can detect similar issues. The feature you see here on the Community is specific to the platform that is…

One more thing to note, any time you add the resolution to a screen it will become a required field, so you should only add it to a screen that is associated with a transition to a done status and the user should be able to pick the resolution.

What you see next to the Done status is the resolution, this is what tells Jira if the item is closed or not. You should never create/use a resolution called unresolved/none, any issues that has the resolution field set to a value are considered as resolved. You can learn more about best practices using the resolution…

@DANIEL FERREIRA DE SOUZA, the documentation you are referring too only applies to Data Center, the API for Cloud, which the question was for, is different. 

Hi @Brooke Fail, Welcome to Atlassian Community! Automation cannot be triggered on incoming emails, it runs after the issue has been created. But once the issue is created you use the text string smart values extract sub texts. You could use substringAfter( String separator) to get the project name and component. 

Hi @tpascal, I have notified the support team that is on here and they should be able to help you. Expect to hear from them within 2 business days. 

Hi @Allan Oliveira Marinho, Welcome to Atlassian Community! I have notified the Atlassian support team that is on here and they should be able to help you. Expect to hear from them within 2 business days. If you are on a Standard plan or higher your other option to contact support is via support.atlassian.com as well.

Hi @Phuong Hoang Welcome to Atlassian Community! Your first one would show issues that has been created within the year, not the ones that are older then 12 months. You would have to change it from less than or equal (<=) to greater than or equal (>=). You can find out more information about operators that can be used in…

If you are using Bitbucket Cloud the URL would look something like this: bitbucket.org/workspace_name/ If you are using DC it would usually look like this: bitbucket.mycompany.com/...

One way would be to export your MS Project file to csv format and import it that way. You can find all the information for it in this KB. Your other option would be to use an app from the Marketplace that would allow you to integrate MS Project with Jira and import that way.

Hi @Diana Viktorova, Welcome to Atlassian Community! The only way to run scripts from an automation would be if you can access the script via a web request. Automations cannot run scripts that are added as an attachment. 

Hi @delson, Welcome to Atlassian Community! Currently it is only Data Center versions of Bitbucket that have EOL dates, which you can view here. Bitbucket Cloud is continuously updated so EOL does not exist in Cloud. If you are on Bitbucket DC and on a version that has been EOL:d then yes, you would be less safe since you…

Hi @Lautaro Nahuel Fernandez, Welcome to Atlassian Community! The permissions depends on what permissions the user have, so if the user is a Jira admin the token will allow you the permissions. If you want to limit what the token allows you to do you have to limit the permissions for the user it is associated with.