Dave Meyer Atlassian Team

Hi @Brian R, Stay tuned. We expect to have an update to share in the next month or two. Regards, Dave

Independent projects are not a "project type". The recommended approach if you already have independent projects and need to create an export for Jira Server is to create new projects in Jira Cloud based on one of the other project templates and move the issues into the new projects. We've added new options to the "Create…

Hi Scott, By default, we require all Atlassian account passwords to be a minimum of 8 characters. We do not enforce any other requirements around resets or expiration without an Atlassian Access subscription. Hope this helps. Dave

Hi Megan, If you've connected G Suite to your Atlassian site, users will log in with Google (https://confluence.atlassian.com/cloud/how-g-suite-users-log-in-744721643.html) If users enter their email address (that you have claimed via G Suite), they will be redirected to Google to authenticate. Implicitly, this means they…

Hi @Marc-André Goderre, To transfer your issues to another project based on a different template, simply create a new project using the template you would like, then use Jira's "bulk move" functionality to move issues from one project to…

Hi @Richard Plumb, We made the difficult decision to remove these unsupported gadgets last year as part of much larger infrastructure infrastructure work we were undertaking, as noted in the deprecation notice. While we definitely see the value in these gadgets, they just weren't widely used enough for us to justify the…

Hi @Mike Daly, You can enable the condensed notifications by opening the configuration page from your Slack channel. In your channel, type one of: /jira manage /jira info /jira and then from the configuration page for that channel, choose the "Compact" message style. Cheers, Dave

Hi @Ben Novack, If you are confident that the user has the "Administer Jira" global permission and can access the rest of Jira Administration like system configuration, add-on management, time tracking configuration, etc but can only create projects with the Agility template, I recommend contacting Atlassian Support so we…

Hi @Daksh Jotwani, Currently projects created with the Agility template only support Story issue types. We are working hard to bring customizable issue types to the Agility template ASAP. In the meantime, if you create a project with the Scrum, Kanban, or Bug Tracking templates you should get the Bug and Task issue types…

Hi Joseph, totally understand. I'll take your feedback to the team to inform how we prioritize adding this back to the Project Details page. In the meantime, it's still possible to update the project lead via the Jira REST API. You can do this by running something like: curl -X PUT \…

Hi @Joseph Niemiec, thanks for replying! Where do your users normally find this? On the project list page?

Hi everyone, Currently it's not possible to change the project lead for projects created with the Agility template (it's not related to the old vs new UI change). We would love to hear what you use the Project Lead feature for so we can understand how we can incorporate it into the Agility project template in an improved…

@Matt Doar the ability for non-admins to create projects is granted by the new "Create independent projects" global permission: https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html FYI this is Jira Cloud only. No plans to bring it to Jira Server in the foreseeable future.

Hi @Barrie Treloar, I'm a product manager on the Jira Cloud team. I totally agree with you that there's plenty of room in both our products and our documentation to reduce the friction for teams to set up a process that works for them using our software. At Atlassian, we strongly believe that no two teams are alike –…

@uday_mishra_ go to the custom fields page in your JIRA instance (someting.atlassian.net/secure/admin/ViewCustomFields.jspa). How many custom fields called "Team" are there?

Hi Uday, What do you mean when you say "It was giving me an error". Is this after you added the Issue Field module to your add-on and installed it in a test instance? Did your issue field appear in the custom fields list in JIRA administration? I would recommend not naming your field "Team" as this is also commonly used by…

Hi @Pavel Bulanov, the function is definitely still available and working fine. I'm working with our documentation team to see why it's no longer visible in the docs. Here's a screenshot of the documentation in the meantime:

No, for JIRA Server the JIRA Suite Utilities plugin is still available for free and supported by Beecom.

Already implemented. We will be rolling it out over the next couple weeks. Dave

Hi Christine, See my answer just above. Dave

Hi folks, I'm the product manager of the team working on this. Yes, JIRA Suite Utilities is being deprecated; however we will support all existing JIRA Suite Utilities workflow validators, conditions, and post functions natively in JIRA Cloud. We are working on this right now, and if you have a workflow configured with one…

Go to the JIRA Software download page (https://www.atlassian.com/software/jira/download) and choose the "OS X" option. That's the .tar.gz archive. We are going to update these options in the next couple weeks to be more clear. We've been attempting to simplify the download pages and it's apparent we've gone a bit too far :)

Hi Kevin, If you have JIRA Agile (I'm assuming you do because you tagged your question with it) you can download the new JIRA Software installers here. You can also read about upgrading from JIRA + JIRA Agile to JIRA Software on the new Atlassian Migration Hub. Cheers, Dave Meyer JIRA Product Manager

Hi @J Kingsly Mano Doss, Unfortunately it will not be possible to test the new resources in your own instance until the SOAP API has been removed. However, you can run an early EAP release on your own server of JIRA 7.0 to test the new REST resources. A draft of the JIRA 7.0 REST API documentation is now available for you…

Hi @Mark Andrew Borg,This is because we released an update to JIRA on 16 August that changed JIRA's behavior. As I mentioned here (https://jira.atlassian.com/browse/JRA-44681) we believe JIRA is now behaving correctly, and the previous behavior where the subtask would transition even if the parent issue transition failed…

Hi @Mike Lamoureux,The reason that both checkboxes are automatically filled in when you try to assign a new user to JIRA Core is that the jira-users group has access to both JIRA Software and JIRA Core. When you check the box to assign the new user to JIRA Core, it's placing the user in the jira-users group, but since…

Hi Guy,There's a fairly comprehensive permission schemes REST API (new in JIRA 7) that will allow you to get existing permission grants and grant them to a new group: https://docs.atlassian.com/jira/REST/ondemand/#api/2/permissionscheme-createPermissionGrantHowever depending on how many permission schemes you have, it may…

Hi @Guy Morton, When you activated JIRA Core from the "Discover New Applications" page, a jira-core-users group should have been created for you. Unchecking the "JIRA Software" access and checking the "JIRA Core" checkbox should place users in this group. If the JIRA Software checkbox keeps getting reselected when you…

In general, JIRA follows Maven semantics. Our public releases follow the MajorVersion.MinorVersion.IncrementalVersion pattern. EAP releases are development builds. We release them to plugin developers before every new minor version. They follow the pattern of MajorVersion.MinorVersion.IncrementalVersion-Qualifier.…

Hi @balvant biradar, You should create a support request at support.atlassian.com and we will be able to help you. Cheers, Dave