nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Epic link field is None when creating task under Epic

Vinod Kotiya

I have company managed software kanban project on cloud. There is problem with one user is that when he creates task under Epic. The epic link field becomes none and the task goes missing. We have to manually set the field each time after searching it with keyword. Though Epic is assigned to him.

While others user are creating task under same epic. The epic link field contains name of epic and it shows under epic. Though Assignee is that user having problems.

What could be the problem.

Accepted answers

Vinod Kotiya

I found the problem. The problem was coming when task is created in roadmap or in epic screen.

Only administrator role can create task under epic. It will link epic in the task by default.. [In roadmap or epic screen)

If any other team member try to create a new task under epic the task epic link is set to none.

Solution 1: Make all user administrator (Not practical)

Solution 2: Tell users to create task by clicking create button > Choose issue type.

I don't know why it is killing UI/UX of JIRA. Why this small feature is missing. Why by default epic link is coming none for non admin users?

All comments

Vinod Kotiya

I found the problem. The problem was coming when task is created in roadmap or in epic screen.

Only administrator role can create task under epic. It will link epic in the task by default.. [In roadmap or epic screen)

If any other team member try to create a new task under epic the task epic link is set to none.

Solution 1: Make all user administrator (Not practical)

Solution 2: Tell users to create task by clicking create button > Choose issue type.

I don't know why it is killing UI/UX of JIRA. Why this small feature is missing. Why by default epic link is coming none for non admin users?

Vinod Kotiya

I found that all these is caused by permission and role. I just restored the permission to default and now Epic is linked with the task created. So I don't need automation. It seems we have to rely only on paid 3rd party app even after buying JIRA license to manage access control.

Vinod Kotiya

This is the screenshot where I messed up with permission. Don't use Current Assignee in Edit Issue. Otherwise when they will create issue then it will not be linked to Epicby default.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud