Hello, Atlassian Community!
My name is Syed Masood, and I am a Principal Product Manager for Jira Software and Data Center. Jira Software 8.0 is here–– and I know you have questions. I'm looking forward to answering all of them.
And we’re live! We’ll be on for the next two hours to answer questions. Please feel free to ask yours if you haven’t already! We’ll do our best to get to as many questions as we can.
Whether you’ve got questions about planning your upgrade to 8.0, want to hear more behind-the-scenes details about planning the release, or anything else - we’re here to chat! Check out the Jira 8.0 announcement blog for more info.
Hi Syed! I'd love to hear about how the Atlassian team is making upgrades easier for users. I know you all have done a lot in the last year to make this process smoother - but I'm curious to hear about the next steps.
I know there was discussion about more 'smart upgrade' functionality.
Great question, and thanks for being the first one to ask! We have big ambitions to make upgrades easier for our customers, and we’re hopeful that our first few steps on this will start to make a difference in this area.
We recently introduced the pre-upgrade planning page in Jira Software Server, which helps streamline the process of upgrades by highlighting important steps and taking care of a number of manual checks for databases, licenses, modified files, etc.
Some of the 8.0 improvements - shorter index time and revised documentation - should help with upgrades, but it’s another small step.
One piece of feedback we are hearing often is about apps complicating the upgrade process. We are exploring the best ways to address this. Your feedback on this would be much appreciated!
Why does Atlassian seem to push story points versus time estimates rather than allowing choice?
(For example Kanban boards don't do time tracking and the 'new look' Jira puts story points into the form for issues even when they're not in the screen they're derived from.)
I can’t speak for some of the newer Jira Cloud experiences, but on Jira Cloud classic projects and Server, you have the choice to configure estimates. Here’s an article that details how to change up your estimate options. For some more of our recommendations on estimating with Jira, I’d recommend this article from the Agile Coach.
Hey there Danny, good question! I’ve answered Meg’s version of it above.
Is there any plan to prioritize and actively work on this soon? The public issue is
It was created in February 2013, and at last count, has 170 comments. The comments are updated/added to regularly; the last one was yesterday.
There is obviously a critical need for this feature and I'm seeing a lot of frustration in the comments thread, which I share.
A lot of us work with boilerplate epics/stories that are repeated ad infinitum, and it's an *incredible* pain to create them manually.
Hi Syed - thanks for the answer. I understand that this is on the 'longer term roadmap,' but that is incredibly vague and doesn't give me a lot of hope, to be honest.
Given the number of "+1" comments in the public issue--it's gone up to 172 since I posted my question on February 12--how much additional user feedback can possibly be needed to prioritize this?
If you consider the number of people who actually connect with the feedback system for any product is in the low single digits of its broader user base, any request with +172 points has the probably actual requestor base (i.e. a representative sample of the affected user base) is in the THOUSANDS.
So, I'll +1 @Paula Kingsley
question of ....can you be more specific about what is meant by "longer term roadmap".
If by "longer term", we mean....we'll get to it before we implement other things that make us look more competitive with Rally, not good.
If by "longer term", we mean...There are some fundamental architectural concerns that we have to work up to, that will then enable us to more properly address this issue, then I can respect that.
the project archiving feature is currently for Data center only.
Would you consider bringing this feature to Jira server, too?
I'm asking because server are of course limited to one instance only. Therefore, reducing index size by removing projects and their issues / comments from the index would greatly help us server customers :)
One more thing:
Why is the release version '8.0.0.release'? This there any reason behind the '.release' or is this a bug?
We are not planning to bring Archiving to Jira Server at this point.
Our process for deciding if a feature should be Data Center-only is outlined here – https://www.atlassian.com/blog/announcements/prioritizing-features-server-data-center
Why is the release version '8.0.0.release'? This there any reason behind the '.release' or is this a bug?
This was a one time exception to work around a Marketplace quirk. Future versions will follow the X.Y.Z naming format.
Hi Syed, We use JIRA extensively and I am currently exploring Next Gen project for few teams. Few questions:
1. What things to keep in mind when migrating classic project to Next Gen project?
2. What kind of reporting is available in next Gen project? We record Burn down, Cycle tiem and velocity. is it available?
3. Is Next Gen project release is stable enough to migrate? I am bit worried incase there are major bugs. We follow Scrum and we have few boards with parallel enabled sprints.
4. How to configure roadmap board so that the highest priority epic shows up on the top? Something like Group by- Epic (available), and highest priority first (not available I guess).
Hi Syed, I'd like to hear how to download or view resource level activities added in Calender? I mean lets say one person has added all his holiday and training acvtivities in a calender. How to see all of his item for a month / year, in list view or text should be fine.
There was an update this past weekend that has changed our views. There is a button to click 'see the old view' but it is not staying and reverts back. This is causing us issues. Is there a way to make the old view stay or something that gives us the option to choose which view works best for us?
It's funny you ask; I was able to figure this out last week. Saved my team the re-occurring headache.
Follow up question: Is there a way we can keep the old view for years to come? Doesn't seem like many people on the forums have anything good to say about the new view.
This is a very interesting problem that you’re touching here and is a source of many debates in Agile world.
To be clear: No.
In Jira Software Server, sub-tasks are not included in Jira’s agile reporting, and they don’t carry story point estimates. The standard burndown chart does not include them.
This is a deliberate behaviour as Jira Software Server, by default, does not allow any estimates on the sub-tasks level. Whilst it is technically possible to enable such field in particular project - it will not work as the system was never designed for this additional layer of complexity.
We are constantly monitoring changes in the Agile movement and talking with our customers on regular basis to help them to help us to better understand how they use Jira.
We do see how expectations towards around this functionality have changed over time, and while Jira Software Server does not currently address this particular need, we are looking at how our customers estimate their work and are proactively seeking for solutions that could potentially address all their (sometimes very much contradictory ) needs.
If you’re interested in this particular functionality, please follow and vote on this request:
When is Jira going to address the disparity between the metaphors (Task is an Issue at the same level as "Story", but "Sub-tasks" of a "Story" cannot be reported upon with progress reports). What???
Here...you want a suggestion for how it should work.....look at this..
Either you make the "Story" Swimline view, which groups by sub-tasks, also supported in the reports where your burn-up and burn-down show progress by "sub-task" (whereas right now you only show progress by "Story" or by "Issue").
You support a view for the Active Sprint to allow groups by Story with all "Relates to" links (i.e. Issues) pointing AT THAT STORY, categorized underneath it.
Fix this...and it will be INFINITELY more aligned with how the vast majority of Scrum Teams use their Scrum (Kanban) Board.
What if you aren't using SUB-TASKS, because the Burn-Up reports don't report completed Sub-tasks as "completion" (which if it was working the way it SHOULD, it WOULD)?
How would one do that.
|| Relates to
How do we monitor progress when Jira operates so illogically in this regard?
If you're going to have Swimlanes to monitor Story progress by viewing Sub-tasks in the active Sprint, then support reporting the Burn-down or Burn-up via counting sub-tasks.
Hi Marcelo, thanks so much for your question and suggestions
You’re right that there are some conceptual challenges with Jira terminology and hierarchy today. That has implications for what is included in Jira’s reports as well.
We are looking into this area of hierarchy of Jira issues and hope to be able to provide some more options for you soon!
Part of your question about reporting on sub-tasks are similar to Karl’s question above. Because subtasks don’t have estimates, they are not included in Jira’s default reporting. However, as you’ve pointed out, this creates challenges around tracking sub-task completion. If you’d like to see this change in the future, I’d encourage you to follow and/or vote on the feature suggestion I mentioned in the answer above (https://community.atlassian.com/t5/Jira-questions/Re-Re-Upcoming-AMA-with-Syed-Masood-JSW-Principal-Prod/qaq-p/1013812/comment-id/324978#M324978).
I have followed and voted for the issue you mentioned, thank you.
I find this particularly pesky, because it's a typical pattern for an agile team to decompose the WHAT (Story) into HOW's (Tasks/sub-tasks), and then to be able to visualize their progress to DONE is powerful (we actually print out the burn-up on a daily basis so they get a tangible record of what their progress looks like as it's changing).
I encourage you all to pursue this with fervor. The fact that a plugin exists to "Count" (SumItUp) issues is preposterous. What's insulting is that one would have to pay for something that should be CORE to the OOTB experience. Guys, we pay good money for our Enterprise solutions, the CORE experience should include things like this, no question.
Hi Jonathan, thanks for the question. Glad you’re excited about 8.0!
Issue archiving is near and dear to our hearts - we’re excited for it to be one of the first new pieces of functionality built on the 8.0 foundation. Stay tuned - we can’t say exactly when, but you should see an update in the next couple of feature releases. :)
Hi @Syed Masood. Thanks for doing this!
Does Atlassian have any plans to improve on the built-in Dashboard options, more specifically, on the gadgets and its layout options in its JIRA 8.x releases??
Dashboards are becoming more common and common for users of all levels and some of the things that I've found to be lacking are:
I'm a power user and a huge advocate for Jira, but the number of times I've had to look something up on a marketplace for basic features are way more than they should be.
My question here is since Atlassian is growing in it's space. I have been an Admin for JIRA, Confluence and Bitbucket past more than 8 years now.
I would like to know how one can best prepare for Certification? I know there is Atlassian Documents but certification questions are most likely Scenario based and answers could be multiple while making selection.
I have attempted one but fallen short of some percentage and would be taking this test again, before I go out now would be better than before.
Your suggestions would be really appreciated.
Hi Akash, great question! It sounds like you have a lot of great Jira experience.
The top preparation tips from Atlassian Certified Professionals are:
Take Atlassian’s Jira Administration Certification Prep Course (USD$150), which you can find linked from this page: https://www.atlassian.com/university/certification/certifications/exam-acp-100
Develop a study plan based on the Certification Prep course, and set aside time for preparation, including researching the exam topics in Atlassian’s product documentation.
Get hands-on experience with the capabilities of Jira that you don’t use regularly in your day to day work, and understand how they could be used to meet business requirements that are different from what you encounter in your own organization.
Form or join a local or virtual study group to learn from others and help them learn. If you have an Atlassian User Group nearby, that would be a good place to start.
Personally, what helped me become an ACP (as of Dec/2017) was really just studying the heck out out of the Jira Administration Certification prep Course as pointed by Syed's 1st point. It has the most studying materials for the price compared to all other modules.
I focused very hard on doing the labs and also what I didn't know. The rest was really just based on hands-on experience (which I had about 2.5 years of just pure Jira admin experience). Sorry if this came off as being unsolicited, but just thought I'd offer my personal experience to you.
Hi @rolejnic, thanks for asking. To help me better answer, can you clarify whether you are using Cloud or server?
Hi Syed - My question may go along here with a few others that people are asking.
Previously as part of the DC Compatible program, vendors were able to opt in by checking a box indicating they were DC Compatible. For Atlassian this program did not give enough rigour around plugins that were running in our customers mission critical instances. Therefore we deprecated the DC Compatible program and replaced it with the DC Approved program. This program involves a deep technical review by Atlassian as well as performance and scale testing. In most cases the original plugins quality has not changed from that under the Compatible program. Though we have countless examples of app vendors making changes to their plugins under the DC program to improve their performance and stability. I understand re-testing these plugins can be a painful transition, but hope you've found these plugins to be a higher quality and the stability of your instances to be improved in the longer term.
Hi @santhi swaroop naik ,
The supported Jira versions can be found on eazyBI documentation page - https://docs.eazybi.com/eazybijira/set-up-and-administer/set-up-and-administer-for-jira-server/installation-and-setup#Installationandsetup-Supportedversions.
The support for Jira 8.0.1 was added to eazyBI on version 4.7.2. Please make sure you have updated eazyBI to the latest version. If the problem persists, please don't hesitate to contact eazyBI support on email@example.com or the contact form - https://eazybi.com/contact.
Roberts / eazyBI support
Hi there, thanks for the question!
Unfortunately, you’re probably using the best macro Confluence has for this task. If you’re looking for something more robust, there’s the Issue Macro from Jira to Confluence app available in the Marketplace (https://marketplace.atlassian.com/apps/1213392/issue-macro-from-jira-to-confluence?hosting=server&tab=overview&_ga=2.40896930.1082177022.1550511443-1291892772.1522981541).
Hi Tobias, thanks for your question. It sounds like you’re talking about the new views in Jira Cloud’s next gen projects. They’re working hard on bringing over a lot of the classic project functionality, so stay tuned! The Jira Cloud team maintains a public roadmap you can follow here.
Hi Alexander, thanks for the question!
It’s definitely possible to have different sprint cadences that are not the same across different Jira projects. I don’t have any handy documentation to link you to, unfortunately, but you can have teams starting their sprints on different dates or sprints of varying lengths within a single Jira.
Hi @Syed Masood
Are you planning on adding more options to workflows in the upcoming versions? Like post-functions (we need to add plugins in order to get some specific behavior that I think should be within JIRA - i.e. assign an issue automatically, add watchers,....)
Hi Fadoua, thanks for asking about this.
You’re right that Jira doesn’t cover the workflow use cases you’ve mentioned. I’m glad the Marketplace has been able to help extend your Jira workflows to meet these needs!
As always, we are considering ways in which users' needs for functionality like workflows are changing over time. Your feedback and requests help us know what improvements would be most helpful for you! We don’t currently have this on our roadmap, but will consider adding these improvements in the future.
Hi @Syed Masood
Does this build address the issue of the memory leak in IE. Currently We have a corporate architecture that forces us to use IE and users have noticed (especially in SD Agents view) that after about a half hour the browsers slows down dramatically and freezes. The only way I have them remedying this right now is to duplicated the tab and close the previous tab (which is a pain). We currently are running on 7.13 enterprise release.
Since launching the Jira Software 8.0 and Jira Service Desk 4.0 platform releases in February, many of you have been asking when the next Enterprise release will be so you can take advantage of the m...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs