Mikael Sandberg Community Champion

It should be further down, almost at the bottom of the list:

You need to be either Project admin or Jira admin in order to see these options.

The app was removed from Marketplace and is now part of Jira Cloud. You should see it if you go to Project settings > Project automation, or Jira settings > System > Automation rules.

I don't think that there are any plans to do that. Next-gen projects limits you on what can be configured, and in order to include multiple projects on one board you need to be able to modify the query for the board. Correct, if you create a board under a classic project you can modify the filter to include multiple…

Hi @amboucher, Welcome to Atlassian Community. The short answer is no, in next-gen you cannot create a board that spans multiple projects. 

Yes, if you automate the merge after a successful build the merge button will only be for show. I would use the REST API to trigger the merge in Bitbucket so your pull request gets updated. The only scenario when this would not work would be if the pull request is not ready to be merged even if the build is successful, but…

It's a good question. I would probably use Jenkins as the gatekeeper for your target branch and have it do the incremental versioning and trigger the merge. You can then build based on the order a pull request comes in.

Git should report any changes you made if you run git status. If it does not show any changes, it will not push anything to the remote repository. You can test that by just adding a new file to the repository and then run git status

You need to be at least Jira admin to be able to see Jira settings, Project admin only gives you access to project settings.

Unfortunately JQL does not have a function that allows you to search on issues in project A and linked issues in project B. You would have to have an app that provide that feature. If you search the Marketplace you will find apps that extends JQL. I have used Scriptrunner in the past and it has a function…

Hi @Jesse Steinberg, Welcome to Atlassian Community. Yes, it is possible to have multiple projects on a board. A board is associated with a filter, and it is the filter that defines what is being shown on the board. Have a look at What is a board? for more information, the last section talks about cross-project board.

Jira settings is only available if you have admin permissions in Jira.

You should only set the resolution when needed. If an issue has the resolution set, Jira consider that the lifecycle of the issue has reached the end. Please see Best practices on using the "Resolution" field for more information.

Hi @Rocke Robertson, Welcome to Atlassian Community. At the moment the integration between Bitbucket and Confluence is sort of non existing. There are a couple of apps that allows you to display content in Confluence that is stored in a Bitbucket repository. Maybe the iFrame macro can be used and just link it to the file…

Have a look at Jira issues need a resolution for instructions on how to set the resolution either via a post function or via a screen.

Resolution is a special field in Jira and is always required and its initial value is 'Unresolved' and cannot be set to optional, there are built-in functionality in Jira that uses this field. You should only add the field to a transition screen when you want to set it or use a post function in your workflow.

Once you do a merge there is no option to roll it back in Bitbucket, and I do not think there is an app that allows you to check if the target branch is being used in a build or not to prevent the merge. How do you handle builds that fails on the target branch? Are you rolling back the merge from the source branch? If so,…

Hi @Christian Barchfeld, Welcome to Atlassian Community. Bitbucket Server do not have a built-in issue tracker like Bitbucket Cloud, your only option is to integrate it with Jira, see Linking Bitbucket Server with Jira

Are you using gitignore?

According to the supported platforms for version 6.10 only Java 1.8 is supported, and there is nothing in the release notes for 7.0.0 rc1 that references a newer version of Java, so assume that it also applies for rc1.

Instead of doing your build on the target branch, you could do it on the source branch and then set up your repository to not allow a merge to happen unless there is a successful build. That would avoid the scenario of having multiple pull requests being merged at the same time.

Hi @[deleted], Welcome to Atlassian Community. If you want a live demo I would recommend that you contact one of Atlassian's Partners and they should be able to help you. 

You can use move to change the issue type, it is under More. You can also do a bulk move so you do not have to go into each story to move them one by one.

According to Statuspage there is no eta, but you can always subscribe and get notified once there is an update

Check your Git config settings and the URL for your repository. If you are using HTTPS, Git will use your config settings to indicate who did the commit.

Yes, it is possible to order by multiple fields, you just have to comma separate them. Example: project = JRA AND resolution = Unresolved ORDER BY issuetype ASC, assignee DESC

Hi @EngiJbell, Welcome to Atlassian Community. Have you made any changes to your repository? If you get "Nothing to commit" it is an indication that you have not made any changes to the repository since the last time you made a commit. 

Hi @Michael Casale, Welcome to Atlassian Community. You have a two options, one is to give the external users access to your network and Jira instance and then use permission scheme and security scheme to control what they can access. If you want to host it on an external space, like Jira Cloud, you would need an app in…

There is a new version of the UI coming for Jira that will look similar to server, have a look at this article, Jira Cloud Navigation Comparison

Hi @Bob_Ash, Welcome to Atlassian Community. Have a look at Insight, they also have an agent free tool for network discovery called Insight Discovery.