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

Accessing field description from a new custom issue type

Varsha Joshi

Hello,

My Jira instance has two issue types defined for capturing bugs. An old legacy one named "Bug", and I recently created a new one "BugV2". BugV2 is more geared towards capturing specific information on the bugs. I was wanting to move a legacy Bug to Bug V2. One of the challenges I ran into was the legacy Bug has a description field which is not present in Bug V2. Once I manually move it, what happens to that data in the original Bug - in this case description? Can that be accessed at all. One workaround I found was to go through the history. Just curious if anyone ran into this and how they resolved it?

Thanks

Accepted answers

Trudy P Claspill

Hello @Varsha Joshi

Are you converting the issue type for issues within a single project, or moving the issues to a different project as well as changing their issue type?

What are the project types involved in this move?

When you say the field is not present in BugV2, do you mean it is not visible on the screens, or has it been removed from the Field Configuration (if this is a Company Managed project)?

If this involves a Team Managed project, is the field a custom field local to the TM project or a Global Context custom field?

All comments

Trudy P Claspill

Hello @Varsha Joshi

Are you converting the issue type for issues within a single project, or moving the issues to a different project as well as changing their issue type?

What are the project types involved in this move?

When you say the field is not present in BugV2, do you mean it is not visible on the screens, or has it been removed from the Field Configuration (if this is a Company Managed project)?

If this involves a Team Managed project, is the field a custom field local to the TM project or a Global Context custom field?

Varsha Joshi

Hi @Trudy P Claspill

Are you converting the issue type for issues within a single project, or moving the issues to a different project as well as changing their issue type?

VJ: Just within the project (atleast for now :-))

What are the project types involved in this move?

VJ: Both are SW projects

When you say the field is not present in BugV2, do you mean it is not visible on the screens, or has it been removed from the Field Configuration (if this is a Company Managed project)?

VJ: It is a company managed project, the field config has the description field but is not used in the BugV2(create/edit screens).

If this involves a Team Managed project, is the field a custom field local to the TM project or a Global Context custom field?

VJ: It is a company managed prject and Description is a global context field.

Trudy P Claspill

I did a test

- with a Company Managed Software project,

- using a multiple-user-select field that is on the screens of one issue type but not on the screens for another issue type in the same project,

- the issue types use a shared Field Configuration, so the field is in the Field Configuration for both issue types,

- filling that field in an issue and then Moving the issue to the type that doesn't include the field in the screens.

Using the information here to find the smart value for a field I printed all the data for the issue after the move. I found that the data in that field was retained.

Varsha Joshi

Perfect! I see it my instance too :-) THank you!

My next challenge is if the issue had screen shots included in the description. The information included in the comments with image is ported seamlessly.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud