- edited description
Migration tool or procedure to move from Project Specific Select Field (simple) to Project Specific Select Field
Custom field type Project Specific Select Field (simple) has some limitations in its use in comparison to Project Specific Select Field resp. Project Specific Multi Select Field.
Advantages of Project Specific Select Field resp. Project Specific Multi Select Field are
- Edit and order of options values
- Allow multi select
- Autocomplete for option values in Jira search
- Available in Pie Chart, Issue Statistics and Two-Dimentional Filter Statistics gadgets
- Works with Configuration Manager for Jira addon
For existing customers it would be very helpful to have a migration tool or procedure available to convert from Project Specific Select Field (simple) to Project Specific Select Field.
Migration tool or procedure would cover the following steps
- Create new PSSF custom field for each PSSF (simple)
- Add the new PSSF to the corresponding screens as it was defined for PSSF (simple)
- Create context for PSSF for earch project covered by PSSF (simple) for the same issue types
- Add the corresponding option values of each project to the corresponding context of the new PSSF
- Bulk change all issue by adding the option values from the PSSF to the issues same as what is assigned as values for PSSF (simple) ideally without changing the last update date of the issues
- Remove the PSSF (simple) from the corresponding screens
- (optional) Delete the PSSF (simple)
Comments (10)
-
reporter -
reporter - edited description
-
reporter - changed milestone to 2.6.0
-
reporter - edited description
- changed milestone to 3.0.0
-
assigned issue to
-
reporter - edited description
-
reporter - edited description
-
reporter - edited description
-
reporter Maybe steps 1, 2, 6 and 7 could be done manually by the Jira admin as part of pre- and post-migration activities, so that the migration tool does not need to include this functionality to avoid too much complexity in implementation of the migration tool.
-
reporter For implementation of step 5 there is a relevant article here.
-
reporter - changed milestone to 3.1.0
- Log in to comment