Mikael Sandberg Community Champion

Next-gen projects do not have the notion of global fields, instead each next-gen projects is almost like it's own island. If you create a custom field in one next-gen project, it is not available for any other projects that you have. Same thing goes with custom fields that you created of your classic projects, those are…

If you go to the Backlog in your board you should see the arrow button to the right of the epic

Hi @Greg Fox, I moved your question to the Confluence collection. 

Hi @Marcelo Bettarello, Welcome to Atlassian Community! Epics are a bit different, they have both the issue status and an epic status. Epics that are not set to Done in the epic status will show up on your board, regardless of what the issue status is set to, see Linking epic status to the epic issue status for more…

Here's my home office... The Funko collection (Prince and Mr Rogers) is my wife's.

It was at the beginning before they changed the limits, but Atlassian really listened to the concerns and changed the limits. Here is a FAQ that they created. My company is a former Automation customer and we rely heavily on it and have close to 20,000 executions in a 30 day period, so we will most likely stay on premium.…

And here is more information about the Automation feature.

Automation for Jira is an app that Atlassian bought earlier this year and they have started to roll it out to cloud customers this week, see this thread.

One option is to use Automation and have it create the issue for you in JSW, you can either do it when the issue is created in Jira Service Desk or when it reaches a certain status, have a specific field value etc.

Hi @kesing_huang, Welcome to Atlassian Community. Do you want to delete the branch and folder that you circled? If so, just expand the folder, right-click on the branch and select delete. This will delete the local copy of the branch and also the folder. Folders is a great way to organize your branches, and are created if…

I would look at the commits that have been done recently. Bitbucket has its own gc that is more affective than git gc. Removing branches/tags have not affect on the size, since they are just pointers to specific commits. You need to clear out your history in order to reduce the size. Please see this guide on how to do…

Hi @dhruv.chheda, Welcome to Atlassian Community. Your project is set up using the Next-gen templates, and as such you cannot modify the workflows (is on the roadmap for 2020). You would need to create a new project using a classic template, that would allow you to change the workflow so you can add the statuses you want. 

Hi @Bojack_Codeman, Welcome to Atlassian Community. There is no option in Git to exclude merge commits when doing a merge. You only option right now in Bitbucket is to use a merge strategy that do not create the merge commit, like Fast-forward only or Rebase fast-forward. 

It is possible, but you have to get all the pull requests and then sort them based on the user. You can use /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests to get your pull requests and then /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId} to get each…

Hi @nicolaterramagrasevenit, Welcome to Atlassian Community. Removing branches in Git will not affect the size of your repository, branches are just pointers to different commits. In order to reduce the size you need to undo the last push and also removing large files from the history. Take a look at Reduce repository…

If you are using Jira Cloud and next-gen projects it is possible to set a default value for Description, and according to the request @Randy linked to they are looking into adding this to classic projects.

See this thread for more information: https://community.atlassian.com/t5/Jira-Software-questions/Automation-for-Jira-Cloud/qaq-p/1281555#M67951

Hi @Matthew Simone, Welcome to Atlassian Community. You could use an Automation rule to do this. We use it to set the component and label field on issues associated with an Epic. Atlassian just started rolling out Automation rules so you should be able to see it under either Project settings or Jira settings.

Hi @hr, Welcome to Atlassian Community. For a new page that has not yet been published yet you cannot choose the option to publish without notifying watchers. If you have already created the page and then edit it you should see this under the ellipsis:

At the moment it is not possible to create a global issue type that can be applied to multiple next-gen projects.

I went through a AD migration about a year ago and as long as the username is the same in both the old and the new user directory there should be no issue. I would strongly recommend setting up a test environment and restore a XML backup from production to it. Then you can test that when adding your new user directory…

Okay, so if Git is not detecting any changes it sounds like something is up with your repository. Do you see the .git directory on the root level of your repository? Are you making changes in a directory that is being ignored by your gitignore file?

I created a brand new Jira Software Cloud instance last week, and it has 27 custom fields, the majority of them are locked, but some are not. So it all depends on your set up and what additional apps you have too.

Not always, the Locked indicator means that Jira or an app has locked it and you cannot change its configuration. If you look at Story Points, this is a field used by Jira Software projects, but you can modify the configuration.

Have you changed the workflow scheme so your tasks are associated with your scheme and not the default one? The Assign button in your screenshot above is not from your workflow, that is the Assign function that comes by default from Jira. Workflow transitions are always to the right of the More button. The easiest way to…

The integration and workflow triggers only support these events: * Pull request created * Pull request merged * Pull request declined (Bitbucket only) * Pull request reopened (Bitbucket Server only) * Commit created * Branch created So the events that happens when someone approves the pull request is not supported, not…

Please note that you have to be Site Admin in order to access the admin page for your subscription.

Hi @mceralde, Welcome to Atlassian Community. Confluence licenses are not the same as Jira, they are separate software with their own licenses/subscription. To manage your subscription, go to company.atlassian.net/admin

If you already have Jira, then you have Jira Core. Jira Core gives you access to Business Projects, Jira Software extends Jira Core by adding Software projects.

If you do not see it, it should be available this week according to this thread: https://community.atlassian.com/t5/Jira-Software-questions/Automation-for-Jira-Cloud/qaq-p/1281555#M67951 I am an existing Automation customer, but I also have it available in a brand new instance that I set up last week.