Mikael Sandberg Community Champion

Another option is to use automation and the scheduled trigger. Then trigger it on a JQL that selects all the issues that you need to set the resolution on. You can then manually run the trigger and disable it once you hav run it.

Okay, so try this. Delete the new repository that you just imported to and creat it again, make sure that you do not add the readme file at the end. When you clone the repository on your Bitbucket server, use git clone —mirror, this will create a bare clone which can only be used for backup. Then when you push it to…

Hi Barry, When you created the repository in Bitbucket, did you choose not to add a readme file in it? The error you get indicates that the remote repository, in Bitbucket, isn’t empty.

Testing my ability to post under bitbucket questions

testing to post here For more information visit https://confluence.atlassian.com/bitbucket/push-versioned-code-to-an-empty-repository-877177145.html 

After you create your epic, you can go to it and in the detailed issue view you should see a button for create issue in epic. You can also do this from the roadmap by clicking the plus sign next to the epic you want to create your tasks in.

If you do not want to hide the Labels field if it is empty you can change that by going to Project settings > Issue layout and move the field out of the "Hide when empty" section.

The Labels field is still available in the new issue view, as long as it is added to your screen. If you scroll down in the context column you should see the show more, similar to this: You can also pin the Labels field, that will move it to the top of the context view.

Yes, boards are associated with a filter, and you can modify that filter to show the information you re looking for. Just go to Board settings > General and change the associated filter.

You are running into a rate limit, please have a look at this thread about it, Rate Limit - Too Many Requests 

Hi @Sayantan Ghosh, Welcome to Atlassian Community! To create a new repository in Bitbucket remotely you would have to use the REST API to do that. Have a look at /rest/api/1.0/projects/{projectKey}/repos for more information.

Hi @Emmanuel Escoto, Welcome to Atlassian Community! Yes, you can finish a sprint even on the free version of Jira. Just make sure that you have the right permissions. If you are using a next-gen project you have to be either a member or admin in order to manage sprints. In a classic project you have to have the permission…

The long answer is not that long... :) Just more detailed on how the integration works. Bitbucket links a commit and pull request to Jira based on the issue key. Just be aware that Bitbucket will not check if the key exist or not, as long as the key look like xxx-xxx Bitbucket thinks it is a Jira issue. 

Check your Customer permission for the project and make sure your Customer sharing is set to "Customers can search for other customers within their organizations, or manually enter the email address of other customers within their project".

You can find the API for JSM here, https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/. Another option to consider is using Opsgenie, since that is now part of JSM. You could then have Opsgenie create the request based on incoming alerts from your server application.

Someone from ServiceRocket can probably give you a better answer, but based on the Marketplace listing for the connector for SFDC & JSM compared to the one for SFDC & Jira is that the one for JSM is trying to link the reporter to a customer in SFDC. So the question is, will your customers submit requests in JSM? If you do…

You have to create a new sceen as well, if you reusing the same screen in your new schema as in the old one it is no different then having all 5 projects using the same schema. Have a look at Project screens, schemes and fields, it gives you a really good overview on how screens and schemes work together.

Hi @Hayley Hinkle, Welcome to Atlassian Community! The short answer is yes, you can have multiple Jira projects committing to the same repository. The link between Bitbucket and Jira is based on the issue key, not the project. 

Hi @IT at Ouachita Hills, Welcome to Atlassian Community! The portal URL is based the order the project is created, and it just picks the next available number, similar to how issue keys are assigned. The number cannot be changed once the project has been created.

Just to follow up on this if anyone else is looking for a solution for this. This is how I solved it. You can use Search for issues using JQL (GET), the JSON result contains approvals. I then filter out the ones that are still pending and use an incoming web hook automation to populate a multi user pick list on the request.

The short answer is no, queues are unique to JSM projects. You can get a similar view in the software project if you create a filter and then use that filter in the Issue view. The issue view allows you to switch between a list view and a detailed view.

You could have more than one team in your JSM project, but since dev team and your other 2 teams will use different workflows my recommendation would be to create new projects for your 2 teams that you are onboarding. That way they can make changes to their project without effecting your dev team.

I am not aware of any other apps besides Refined that allows you to modify the portal, but you may want to check out the Developer community and ask that question there. And yes, cloud is limited in what you can do with the API, but I believe Forge will change that.

Take a look at this thread for more information about automation.

Hi @Alyse Middleton Welcome to Atlassian Community! You can do this by using Automation and a custom date field. Configure your automation rule to reopen the ticket once it has reached the date.

Hi @Jeff Miner, Welcome to Atlassian Community. No, you cannot customize the portal when it comes to the search field. You would need an app like Refined in order to do that, it looks like you can configure the search field with it.

If you workflow allows you to move the request to the other status then you should have that option if you click on the status in the ticket. From here you should also be able to view your workflow. If you workflow do not allow that transition to happen, you can always modify your workflow to allow it. Please note that you…

Hi @Julie Bock, Welcome to Atlassian Community! The @ mention is controlled by a global permission, Browse Users, and can only be updated/changed by your Jira admins.

Hi @Flor Mejía, Welcome to Atlassian Community! Have a look at this thread, How do I create a 'time in status' report in Jira Cloud?, it is mentioning two apps that would allow you to do this.

Do you have different fields in the two projects? Or different issue types? This is what is needed to move issues: Move any issue This permission allows people to move an issue to another project on your Jira site. To successfully move an issue, they also need permission to create issues in the target project. This…