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 getting to know you all) during our upcoming "ask me anything" or AMA event!
Join me on Wednesday, February 20th from 8:00-10:00 am PST for this exciting, live AMA event.
Start submitting and upvoting questions now below (yes, it says answers 😊) I’ll be back to answer your questions live on February 20th!
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.
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.)
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?
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, 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.
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 Syed - My question may go along here with a few others that people are asking.
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.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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