distinguish Agile Elements Epic> Story and Sprints
R
Roberto Mora-Galvis
Agile: Its difficult to have a folder as an Epic, then a task list as a story when one cannot add Sprints within a folder.
Log In
R
Roberto Mora-Galvis
I guess no much benefit, its a workaround. so, you may be right. But we need , I am sure anyone who works with an Agile methodology, we need to be able to have Epics that have one or several stories (like Jira). Either I dont know how to set it up, or the workaround I am creating is not intuitive to be followed by the different departments.
NOTE: Epics are usually what Sprint, Sprints, Quater, year GOALS, are based on as well as included in KPI. We use them for development, Marketing and Sales. So, one must be able to report just on Epics
One Simple solution I think is within a list, for task(s) to be able to become "Epics". These tasks are like parent tasks to subtasks, however, they behave differently: They are bolded, they cannot be assigned to a Sprint and all may have a different Status to follow i.e: TO DO, IN PROGRESS and DONE. While the children's tasks may have more complex status workflows.
One of the solutions, more complex on your end, but still easy to grasp for end users, it would be to have the option, under "Create New", to have another list option called something like "Epic List", OR, to be able for any list the functionality to "become" an Epic List. where, unlike other lists, It needs to be associated with another existent lists or lists. In this Epic list, the tasks are the epics and the subtasks the stories but behaves differently.
In the "Epic type" list(s), the main tasks are the epics and stay in the list while the subtasks would be the stories and "only them" would "automatically" be added up into any other list or lists pre-determined by the user, for instance associate the Epic list to the list "Backlog". The rule is that for a list to have the feature type of Epic it must be associated with another list(s), otherwise, it behaves like any list
On the other hand, the list associated with the epic, i.e: "Backlog" behaves same as any list, just that most tasks are children of Epis in another list. These ways, only stories not epics can be assigned to Sprints.
.. Sorry for my looooong explanation, but this is really needed and the only thing we miss from Jira. I hope it helps.
R
Roberto Mora-Galvis
THIS OPTION IS USEFUL FOR SEVERAL OTHER NEEDS. Another is when using a whiteboard template for Retrospectives. when in "list" view, "liked, lacked, Learned and Longed" would be like Epics, while the inputs from the teams would be the tasks; Another is to introduce a "view" as a document. Story is the doc title, epics are the H2, Stories H3 and Tasks and subtasks bullet lists underneath and all description are paragraph. They can be printed out for any business meeting or included in a PowerPoint presentation!
Sean Kilcullen
Roberto Mora-Galvis what are the benefits of having an Epic as a Folder? I typically create Epics as a task, then use Relationships to connect other tasks to it or use subtasks.
A
Adam
They are currently working on Sub-Folders, I assume with that layer of functionality you would be able to create a "Sprint Sub-Folder", I've pasted the link below for you to follow!