Mikael Sandberg Community Champion

Hi @Hermin Lalefar, Welcome to Atlassian Community! You can change the order by clicking on the header, if you click the Components header you can sort the list alphabetically.

Hi @Hareet Gill, Welcome to Atlassian Community. Currently it is not possible grant edit permissions to a group on Jira Cloud, and according to this request, JRACLOUD-17783, it is no plans in the near future to add it. 

Hi @Mauli, Welcome to Atlassian community. You can use the REST API to get the members. Here is the documentation for Jira Cloud with an example on how to get it, API group project role, and here is the documentation for Jira Server, api/2/project/{projectIdOrKey}/role

You would need an app in order to do that. Advanced Roadmaps allows you to set up the version so it is relative to the previous release date.

Hi @Kevin Pannell, Welcome to Atlassian Community. You can accomplish this by using Automation rules, and it is part of Jira. Depending on the plan you are on, there are some limitations to be aware of. Have a look at Jira automation for more information.

Do you have access to both projects? If you have access to the target project it should be listed in the dropdown, you should not have to manually type it in.

Yes, from a developer standpoint that is it. If you re using the Release hub in Jira and the version release/build and release feature you will get a warning if you are trying to release a version that still have open pull requests. As an admin you can add triggers to your workflow like I described above. And the…

As @John Funk mentioned, you need to change the permission scheme and limit who can browse the project. Or create a new permission scheme if you do not want to affect any other projects that you have.

You can move a repository by going to the repository you want to move, select Repository setting and under Repository details you can change the project. 

If you remove the site access the user will not get any notifications. The user will be considered deactivated and will not be considered by the notification scheme or any filter subscriptions.

Both your options work, you just have to decide if you want to do the upgrade work on the source instance or do the migration and then do the upgrade on the target instance. Does the source instance need to be available for your users while you do the upgrade? When I was on Server the way I did it was standing up the new…

I would recommend using project roles instead of a group, that way the project admin can manage who belongs to that role. If you use a group you need Jira admin permissions in order to add remove users. Have a look at How do Jira permissions work?, it gives you good overview of how roles works.

Correct, the main interaction a developer will have between Jira and Bitbucket is the Create branch, that will forward you to Bitbucket to create the branch name consisting of the issue key and the issue summary. You can either just confirm the name or make changes to the name. At my previous job, most of the developers…

Yes, it is Git Integration for Jira that is giving you the error message you see (the red you see under Manage apps just means that you need to upgrade the app). That app is not needed if you are using Bitbucket, and you have already set up the Bitbucket/Jira integration. I would consider to at least to disable the Git…

Have you tried using an incognito Chrome window? Also, are you using any Chrome extensions like ad-blockers?

Yes, the error is coming from the app, and you can can go to add-ons > Manage add-ons to see what apps you have installed. The screenshot you included above is for Applications links, which is different from add-ons/apps. And since you have Bitbucket you do not need an additional app for Git, unless you have Git…

In Jira Cloud you can only import workflows that are hosted on Atlassian Marketplace. This KB describes what you need to do.

Hi @Jake Barber, Welcome to Atlassian Community. To completely wipe Sourcetree you have to remove the Sourcetree folder under appdata\local\Atlassian and the Sourcetree folder under local. You should then be able to reinstall it. If you just want to redo the initial setup you just have to remove the Sourcetree folders…

Hi @Miranda Montoya, Welcome to Atlassian Community. You may want to add some more information about what you want to do so. Are you looking to get a list of issues and export them? What custom reports are you looking for?

Hi @Manoj Kumar MK, Welcome to Atlassian Community. If you want the field to always be required you do that in the field configuration that you will find when you go to Project settings > Issue types. Your other option is to only make it required on specific transitions, then you have to edit the workflow and add a…

The short answer is no, you cannot limit what branches/commits you see in Jira. The only way of doing it would be to only mention the issue on commits for a specific branch.

Hi @Andres Mac, Welcome to Atlassian Community. Advanced Roadmaps is only included if you have Jira Software Cloud Premium, on Jira Server you would have to buy the app separately.

No, if you have the Premium plan it is available for all classic projects. See Jira Software Premium to see the differences between the plans.

Yes, but you need to be on the Jira Premium Plan in order to have access to Advanced Roadmaps. On Jira Standard Plan the roadmap is only available in next-gen projects.

One option would be to use JQL condition to figure out which Slack channel the notification should be sent to, that way you do not have to have a field on issue that identify the organization. Your query would look something like this: organizations = "Customer A" Then just build up the rule with if/else blocks for each…

You should be able to do this with Automation rule that you run on issue creation, as long as you have a field in the issue that identifies the customer.

Hi @Matthew Mays, Welcome to Atlassian Community. The commands to undo the last commit has to be executed on your local clone of the repository, and once you have undone the commit locally you push it back to Bitbucket and that should reduce the repository there. 

Okay, so that is not from Bitbucket, if a Jira issue is associated with a branch/commit/pull request in Bitbucket you will see something like this: My guess is that you have Git Integration for Jira or another Git app that has not been configured correctly. If you go to Manage apps you should see it there.

Stash is the old name for Bitbucket Server, Atlassian changed the name as of release 4.0. In this case the remote would be Jira, and local Bitbucket, since the documentation is for Bitbucket. Where do you see Git integration? I guess is that you have an app for Git installed but the license key for it has not been added.…

Go to the workflow that the project is using, you can either do that from Project settings > Workflow and from here edit your workflow. Or you can get to the workflow via Settings > Issues > Workflows and then locate the workflow used in the project. Once you are in edit mode of the workflow, click on the transition that…