Hi there,
some time ago, i created a configuration for a set of projects. One project is used for handling all Epics to provide a brief overview about all the work that is done between multiple teams, lets call it EPIC. Then there's a set of "team projects" which are used as containers for Tasks and Sub-Tasks to the aformentioned Epics, lets call them TP.
There's are some Boards in the EPIC project, which are used for reviewing the incoming work, planning it and have an overview of all the work curently done by multiple teams.
We are also using boards in TP with filters, that check for Epics in the project EPIC with certain components and the Tasks of TP.
To be honest, that works quite well and is easy to use for the most part. Also the Permissions are easy to handle and quite unterstandable for everyone.
The overview we're getting is great, it's easy for users to check which tasks are necessary to get specific epics done and for team planning purposes is also quite great.
But we've got a situation regarding the creation of Tasks for Epics.
Roughly one half of our Users prefer the "Backlog method". They create tasks for a specific Epic via the Epic Sidebar in the Backlog view of their Team Boards and plan them accordingly.
The other half, prefers the "In Epic" Method. They want to create Tasks right in the Detail view of the Epic, because they have a completed overview of all Tasks created for the Epic, whether that Tasks is done or not. That was their standard approach, before we've created the new Set of projects - and here's the Problem - because of the current configuration, they are not able to do that in the team boards we've provided and that feels quite odd.
From a configuration point of view the handling in Jira seems correct, but it feels quite counterintuitive for users.
What would be your approach for such a topic?
