Comments
-
Hi @Elodie Dechaintre - the parent field will be consistent with existing rules for what is considered a valid parent. For example, in company managed projects, you can have a epic in one project but children in another. However in team managed projects, epics and their children must be in the same project. Subtasks must…
-
Hi @Nikki Zavadska _Appfire_ Great to hear it’s welcome news. I’ve spoken to the team looking at changing the kanban cards in company-managed-projects. They said they have no concrete plans as yet to show images, but will be exploring it as an option in the future.
-
Hi @Dave Mathijs, yes the changes are effective for all levels. Technically the parent link custom field doesn't allow you to select an Epic. So for the "below Epic level" example, a task/story/... etc can't have the parent link set to an Epic. But the task/story/.. can have the parent link field value set to parent with a…
-
Hi Vaishali The hierarchy level JQL would be beneficial if you have multiple issuetypes that you want to search on. If for example if you use Jira Software and want to search for all issues on the story level e.g. Bug, Story, Task, you can use the hierarchy level instead of listing each of the issuetypes. As mentioned by…
-
Hi @Magdalena Zhisheva In most cases you don't need to do anything, your epic link and parent link data will be migrated to the new parent field. The only case we won't migrate is if the field data does not conform to the hierarchy configuration i.e the epic link or parent link value is not on a higher hierarchy level than…
