Mikael Sandberg Community Champion

The trial license is valid for 30 days, but can be extended for up to 90 days, see Purchasing & Licensing FAQ for more information.

Hi @Rob Ng, Welcome to Atlassian Community. You could use the same private key for all your users, but then all commits would show up as being from only one user, then you have the problem identifying who made what change. I would strongly recommend having your users set up their own SSH keys.

When you was setting up Jira you were asked to set up an admin account, you can use that one to log on and get to the admin portion. Or you can log in with any user that have Jira admin permissions.

Yes, it is possible to switch between the licenses, all you have to do is go to Administration > Application and change the license key.

And these does the same thing if you are on Confluence Server: https://marketplace.atlassian.com/apps/1211800/glossary?hosting=server&tab=overview https://marketplace.atlassian.com/apps/1217138/glossary?hosting=server&tab=overview

Hi @Libby Morris, Welcome to Atlassian Community. I did a quick search on the Marketplace and found this app that seems to be able to show you a pop up, https://marketplace.atlassian.com/apps/1219677/smart-terms-for-confluence-glossary?hosting=cloud&tab=overview 

Hi @praseeda.sankarankutty, Welcome to Atlassian Community. This blog post, Server vs. Data Center – what’s right for you? explains the difference between server and data center. If you are just testing some Jira Software features I would go with the server license. 

You can add the key as an access key on each repository, see Access keys for more information. Please note that there is no option to do it on a higher level, like the project or your site.

Hi @Luke Prettyjohns, Welcome to Atlassian Community. You cannot limit the create branches/pull requests in the integration. The closest you can get it so set up different groups in Bitbucket. You can set one up that you assign your test team to and only gives them read access to the repository/project. With read access…

Go to the pull request and click the ellipsis button and select Edit. From here you can change the target branch for the pr.

Hi @[deleted], Welcome to Atlassian Community. There should be instructions for how to populate your repository with local code shown if you access your repository in Bitbucket, but here are the steps: * Cd into your directory that have your code * Initiate it as a Git repository by running these commands git initgit add…

Hi @nikitas.papaioannou, Welcome to Atlassian Community. You have the option to edit your own posts, if you hover over your post you should see an ellipsis button appear, and from here you can select edit and modify your post. And yes, anyone that is a community leader/moderator can modify your post too.

It can be done, but you would need to convert the comments into tasks and then configure your repository/project to not allow merges to happen if the pull request have open tasks. 

Hi @Johnny_Trujillo, Welcome to Atlassian Community. You can delete the board by going to Boards > Manage Boards and click on the ellipsis to the right of the board you want to delete. 

Next-gen project doesn't allow you to modify the workflow, so the closed you can get is to set up a new column for cancelled issues on your board, but you will not be able to change the resolution.

Here is a good link regarding resolutions, Best practices on using the "Resolution" field 

Hi @Diego J Vasquez, Welcome to the Atlassian Community. Jira treats issues that has the resolution field as "resolved". You can have different reasons for how the issue is resolved and that is what the Resolution field is used for. If you want to be able to move any issues to the Closed status with the Resolution as…

Hi @Will Bove, Welcome to the Atlassian Community! Expect to learn a lot, pick sessions that you find interesting, the once you miss you can always watch later since all sessions are recorded. Take time to visit the Expo Hall and talk to vendors and come by the Community booth! Also take a look at this thread,…

There is no built-in option, but yes you can do it with Scriptrunner, take a look at this thread, it has an example of how to do it, https://community.atlassian.com/t5/Jira-Core-questions/ScriptRunner-copy-Epic-custom-field-to-every-Epic-child/qaq-p/1042331

@Lama Tatwany correct, Gitlab is not supported, but according to this feature request, JSWSERVER-14412, Gitlab EE 10.0 has an unofficial integration to Jira.

The short answer is no, you cannot limit the change based on specific workflows.

You could use Automation for Jira, we currently rely on to similar things. When we create a task that is associated with an Epic it will automatically copy components and labels.

Hi @heather_king, Sprints are not unique to a project, so if you see changes to a sprint made in one board being reflected on another you need to look into if an issue on the other board is using the sprint in the first board. You should make sure that your sprint names are unique for each project. 

Go to Issues > Search for issues. If you have not used the advance search before it is set to basic, just click advanced and enter the JQL.

In order to modify this workflow you need to have Jira admin permissions, since the workflow is being used by multiple projects. If you have Jira admin rights, go to Administration > Issues > Workflow, create a draft and click on the transition. From here you can select to not have a screen associated with the transition.…

Okay, it looks like your key is set up to only have read access. Did you add your key under access keys on the repository or as part of your profile? If you do it as an access key you will only have read permissions which only allows to clone and pull from the repository.

Hi @reddymanuja, Welcome to Atlassian Community. This JQL should get you all issues that do not have a component: component is EMPTY

Run ssh -vT bitbucket.org, it should tell you where SSH is getting your private key from. 

Hi @Shrups, Welcome to Atlassian Community. As far as I know there are no limitations, I did the migration from Jira server to DC a couple of months ago and the integration to Confluence worked as expected.

Hi @nskforward, Welcome to the Atlassian Community. Did you update the remote URL for your repository to use SSH?