Atlassian Team members are employees working across the company in a wide variety of roles.
August 15, 2018 edited
@Daniel Zimmerman The team is currently working on adding support for epics and it will be available in the coming weeks. I'd love to better understand how you and your team use epics today. If you have time for a call I can walk you through the experience. Feel free to reach out to me at pthompson@atlassian.com and we can schedule some time.
@Maciej Połoński We're glad that you are enjoying the new agility project experience!
1. There are no plans to bring these features into the current software templates. We will eventually work on migrating existing projects into this updated experience but this is still a long way away.
2. We plan on supporting more customizable levels of hierarchy but will release with epics in the near future as a first step.
3. We released Agility as a separate Software template so that we can get feedback as we work on adding more power. In the future, we will offer multiple templates powered by the same project configuration that you have with Agility.
Thanks @Patrick Thompson! On point two, that's awesome as I'd like us to move to Portfolio and have gantt views though it's not quite there enough for us to move from a dog of a system we're currently using.
Is there a road map for these features? Also, is there a view to have Agility templates for business projects?
Atlassian Team members are employees working across the company in a wide variety of roles.
August 20, 2018 edited
@Alex Lock I'd be happy to hop on a call to discuss some of these features and our plans, feel free to email me at pthompson@atlassian.com and we can schedule some time. We are working on publishing an external roadmap for Jira Software and will communicate this out to the community so stay tuned for an update.
I spent a little quality time with Agility Basic over the weekend. We have been using Jira for a while and work in an agile manner. We have our own project workflows that help our team stay on top of issues. I couldn't see a clear path forward for us to migrate as of this time. I have a few issues at this time
1. Create projects using categories. This is important to our reports.
2. Choose project template. We have built our own which includes:
-- workflow -- screens for different issue types -- time tracking Tempo.... ugghhh we need to invoice clients based on issues -- issue field; wow a lot is not apparent here where did created date go?
I would be happy to give some feedback by moving a live project over and running it in parallel. What is the best way to create a new project in Agility by duplicating and converting an existing project?
I am super confused as to why a project would launch without the ability to log work/time at all? I really like the simplicity of the Agility template but I have to track time :-/
We've been busy building out key features in this new project and as you can see, there's still a long way to go. Your input is critical in us making the right calls, so thanks for trying out agility project and providing your feedback.
Currently, we support moving issues from one project to another but with limited configuration options in agility, you might lose some of your custom fields or status.
I'd be happy to jump on a call to see how we can best support you to run two projects in parallel. If you're interested, please find some time here.
Thanks for your feedback. We understand that ability to log time is important to create reports on team's work and we're looking into this at the moment.
Is your team using Tempo or Jira API to report on logged entry?
@Erika Sa We are using Tempo. Can you also explain how I can move my project away from Agility, I have issues in there and don't want to have to recreate a new project. I didn't know Agility didn't do Time Tracking when I started with it :(
It's currently not possible to convert an agility project into another project type (like Business or Service Desk) or to another Software project template (like Scrum or Kanban).
If you need to move to a new project or board type, we recommend creating a new project (you will need to be a Jira administrator to do this). Once you have created your new project, you can move issues from your existing agility project to the new one.
Atlassian Team members are employees working across the company in a wide variety of roles.
September 2, 2018 edited
@Upasna_Bassi We're currently working on our first iteration of epics and they will be available very soon. When you get a chance to use them in your project, I'll be keen to get your feedback on whether they address your needs! Thanks
Atlassian Team members are employees working across the company in a wide variety of roles.
September 5, 2018 edited
@Mikael Sandin Yes, this has moved. Sorry for any confusion this has caused. We recently moved shared configuration out of the list of templates, once you select a template it is available under 'Advanced' as a checkbox 'Share settings with an existing project'. I've attached an image below.
Hello, I spent all the afternoon trying to create a subtask in a task, but I don't know why in my new Software Project this option is not available. Does someone know why I have this difference?
Hello guys, I understand that features are being created as an ongoing development process. I would like to add sub tasks to your to do list. Hope we can get them and Epics some time soon. Keep up the good work
Atlassian Team members are employees working across the company in a wide variety of roles.
September 11, 2018 edited
@Garikoitz Sub-tasks are not available in the new project experience yet. We went with epics as our first iteration work hierarchy and these will be available very soon. Sub-tasks will be the next thing that we pick up.
We're also currently working on making the differences withthe new project experience more discoverable so apologies for the confusion.
Atlassian Team members are employees working across the company in a wide variety of roles.
September 11, 2018 edited
@Zile Rehman, I'm sorry that the experience for multiple issue types is confusing. If you are an admin of your project, you can add (and manage) issue types from "Project settings". We've taken your feedback on board and we will look at how we can make this ore discoverable for new users. Thanks!
@Eoin Ryan It's not a good idea to introduce a new workflows/views that do not have the required functionalities. Also, it's not a good idea to randomly change UX as Atlassian has done as of late.
@Zile Rehman I feel like you're missing the point of Agility boards. They were introduced as "What would a Jira project look like if we started from a clean slate". They're for people who want the power of Jira but without the administrative burden, with features getting added over time - but for now, they're optional.
If you still want the traditional Jira board with all its flexibility/features, just use the old Scrum or Kanban templates. They're still there.
402 comments