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

Moving tickets in the same project clears fields

unknown

I'm trying to move tickets from one issue type to the other. From Bug to Dev-Task

- They are both in the same project

- They have the same screens

- They have the same workflow

I see that the ticket number doesn't change so I'm guessing the ticket doesn't go through a "create ticket" action via the workflow.

These issue types don't have the same fields in the create-edit-view screens: meaning if the ticket has already been created and maybe went through some transitions - it will have some extra fields that don't exist in the create screen).

Should the type that the ticket is moved to (Dev-Task) have the fields the original issue type (Bug) has in the create screen (although it doesn't seem to actually create a new ticket)?

Accepted answers

All comments

Joe Pitt

You say they have the same screens but then go on to say they don't have the same fields on the create screen which disagrees with the first statement. Do both issues have all the same fields, but just not on the create screen?

unknown

Yes.

Both issue types share the same screen scheme, meaning their create, edit and view screens are the same.

Inside these screens: the create screen doesn't share the same fields as edit and view. for example: reviewed by and verified in version/s are fields that appear in edit and view and not in create since these fields are required in the ticket's progress and not in its creation.

Joe Pitt

I don't know why this is happening. As long as the fields are defined in both issues. Is there a different context for each issue type?

unknown

I'm not sure what you mean by context, but they have the exact same fields since they have the exact same screen scheme and screens.

Erica Vorsay

Hi Keren

We have had the same issue and found that the cause is the Request Type. When we move from one issue type to another, the Request Type does not update and is left blank. If we manually populate Request Type, the content is visible to the customer.

Hope this helps

Crystelle S

I'm not certain this is the answer but if someone comes looking, my site admin suggested that in moving from one ticket type to another, a field was marked required, this setting (going from not required to required) can trigger a required update in the move process.. leading the system to clear out the current value. Very old question and probably not everyone's issue, but I am working on Data Center and thought I'd add here in case it helps!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server