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; } } }

Issue Type moved but doesn't show up the custom fields

Arun Unnikrishnan_ul3s5t

I have an issue type Task which I moved to another one - Plan issue type.

The plan issue type has some custom fields and they are not showing.

While a new Plan is created, all the custom fields are shown correctly.

What can be done to show the custom fields when a Task is moved (rather converted to) a Plan?

Accepted answers

All comments

John Funk

Hi Arun,

Can you provide some more clarity? You cannot move an issue type from one to another. You can move issues from one issue type to another. Or you can rename an issue type from one name to another.

Which did you do?

Arun Unnikrishnan_ul3s5t

Thanks @John Funk

Let's say we have 2 issues - Task (Issue 1) and plan (Issue 2)

Task Moved to Plan - It doesn't show the custom fields of Plan that were configured in the Plan screen.

When Plan is created newly - all custom fields are shown correctly.

The issue is only when a Task is moved to a plan.

John Funk

You need to check the Custom Fields to see if there is a Context associated with them that limit their availability to just the Task issue type (or at least do not include the Plan issue type).

Arun Unnikrishnan_ul3s5t

I did investigate and found that the custom filed was not included in the screen scheme.

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