Hello,
I am a new Jira Admin and I have a project structure like this:
Customer(Epic) -> App(Task) -> Task(Subtask)
Which column do I have to add in the Issues list, that I can see the name of the costumer?
Epic Link and Parent Link are disabled and replaced by Parent.
But the Parent column only shows the 1.level higher layer. Therefore I am only getting the App(Task) name when my filter only shows the subtasks.
If it is not possible to do that, is there a workaround you would suggest?
I thought maybe I could create a hidden field with the parentEpic name in it, and show that as a column in Issues?
Thanks.
Hi Bernhard - Welcome to the Atlassian Community!
You will not be able to see multiple levels in a single JQL query. You would need to look at the List view for the project or a timeline view to see those.
Thank you very much. I guess I will have to find another solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are very welcome.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One thing I don't understand:
For example the issuekey PROJ-100 is an Epic.
I can now create a filter-column "Parent" which shows "PROJ-100 <epic-name>" for all issuetypes except sub-tasks. (whereas I/we want - the epic information - also for sub-tasks)
Now I select in a filter like this:
"AND ParentEpic = PROJ-100"
The result is that the system selects all issuetypes:
Epic, Bugs, Stories, Tasks and Story- or Task-SubTasks
although the system has to find the corresponding parent Story/Task-Epic for the sub-task.
Now the problem:
The system can select correctly all issuetypes by ParentEpic but I cannot put this information into a column of the same filter! (because this field "ParentEpic" is not available when I configure the columns)
Why is this not possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.