Mikael Sandberg Community Champion

You can use the REST API to get that information. For Bitbucket Server you can use /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/permissions/groups to get a list of groups that have permissions in the repository. There is a corresponding one to get it on the project level too.

Are you changing status names? Statuses shared across all your workflows, so if you change the name in one it will affect all workflows.

What you see is per design. Project permissions controls who have access to the repositories within the project. So if a user do not have access to the project they will not be able to access the repository, even if they have full permission to it. See Using project permissions for more information. 

Pull does not have a force option, only push. For pull you can use the option --allow-unrelated-histories, that will also disable the merge check similar to the --force on push. Have you made any changes in your local repository? If so, have you pushed those changes up to Bitbucket? If you have not pushed/made any changes,…

Hi @karson tse Welcome to Atlassian Community. By default, git merge command refuses to merge histories that do not share a common ancestor. You can override this by using the --force option, this bypasses the checks and may cause the remote repo to loose commits, so be careful when using it.

Hi @vijender mali Welcome to the Atlassian Community. Only Jira keys that are part of a commit comment will show up in the commit list. If you enter a key in the pull request itself it is not associated with a commit, it is only associated with the pull request itself and there is no way of changing that unless you amend…

Hi @Josh Kalsbeek Welcome to the Atlassian Community. This guide, OAuth for REST APIs, should help you setup the application link. Skip the Before you begin step, that is only if you are developing your own app.

If you still have a clone that still has the branch it can be recreated that way. Deleting a branch in Bitbucket will not delete it on any of the clones. Git do not keep track of deleted branches, they are just pointer to specific commits.

Hi @Minna Song Welcome to the Atlassian Community. The roadmap feature is only available in Jira Cloud, and only if you are using a next-gen project. Jira Server does not have these features.

I'm in...

I am still using internal groups in Jira, that way I do not have to rely on our IT helpdesk to add users to the correct AD group. All I did was exporting out the members in the current groups using REST API, fix the user ID (stripping out @XXX.xxx from the email adresses), and re-add them to the correct groups. You could…

Just out of curiosity, is there any particular information you are looking for or have questions about any of the tools?

Hi @Brandie Baker Welcome to the Atlassian Community. Atlassian does not have a typical sales organization. If you need to talk to a sales person, your best bet is to contact one of their partners and they should be able to help you.

Make sure you read the complete guide, especially step 6 since you are going to a new major release and any customization you have done will not be migrated automatically.

Does your workflow have a condition for the scripted field that was removed? One thing you could try is to make a copy of the workflow, change your workflow scheme to use this new copy of the workflow and see if that helps. 

Yes, switching user directory from an internal to an external will keep the ownership, as long as the usernames are the same in both directories. I went through a similar exercise a couple of months ago when we switched domains and at the same time user IDs. There was only a handful of users that got their avatars reset,…

Jira does support nested groups, but you can only nest internal groups in internal groups, or external groups in external groups, not external in internal or vice versa. It looks like Crowd allows you to nest an AD group to an internal group (jira-administrators), see Nested groups in Crowd. 

@Benjamin Weinheimer-Erben _mgm-tp_ I just checked on my instance and I do not see this behavior. Are you using Jira Server or Cloud? Did you change your screen scheme so it is using the screen that does not have the custom label field for Edit Issue operations?

Smartsheet has a connector to Jira, https://www.smartsheet.com/s/smartsheet-and-jira. You have to contact Smartsheet to get it.

This query will get you all issues in the project that has at least one pull request associated with it: project = JRA AND development[pullrequests].all > 0

You can use JQL to query on the development information using these searches: * development[pullrequests].all (or .open) * development[commits].all * development[reviews].all (or .open) * development[builds].failing You cannot search based on the branch, at least not yet.

To change the logo, go to look and feel under Settings > System. From here you can upload the logo you want. See Change your site logo and colors for more information.

Do you get an error message when starting up Jira? Have you checked the Jira logs to see if an error is reported?

Hi @Amit Sahu Welcome to the Atlassian Community. The database is needed because Bamboo stores plan configurations and build results data in the database.

Hi @Akisha Anthony Welcome to the Atlassian Community. You can find the documentation for how to migrate to a new server here, Migrating Jira applications to another server Basically what you will be doing is installing Jira on your Windows server, do a xml backup on the Linux one, restore it on Windows and then move…

Hi @Krista VonCannon, Welcome to the Atlassian Community. None is just a display value, so in your JQL you should use EMPTY as the value to find issues that do not have a value for your custom field.

You would need an app to do it. I use Scriptrunner to show/hide fields, but you could use other apps to do it too, for example Power Scripts or Secure Fields depending on if you are on Server or Cloud.

@Hyd3k It was released as part of Jira 8.3 which was released a couple of weeks ago.

On the detailed issue screen, select Worklog next to Activity and from here you can delete an entry.

Hi @Abhi, Welcome to the Atlassian Community. Short answer is yes, you can have sprints starting on different dates within the same project. Just make sure that the sprints have unique names, since they are not tied to a specific project, they are available to the whole instance. And yes, each board has their own reports…