Impact of changing Userpicker field?

[Darryl St_ Pierre]

We currently have a JSM project that has a field configured as User Picker (multiple users). The field should be User Picker (single user). Instructions on the submission form request one selection but occasionally someone selects more than one.

I want to change the field so that it is correct going forward but I'm concerned about impact on existing issues. I'm assuming that I need to create a new field to replace it in the submission form, and since it's tied to an approval I'll need to either update the existing workflow or create a new copy that uses the new field. Either way I feel I'll lose either history or reporting capabilities on the existing issues.

Am I overthinking this?

[Hannes Obweger - JXL for Jira · Accepted solution]

Hi @Darryl St_ Pierre

you're correct - Jira doesn't allow changing the type of a field, so you'll have to create a new field, and copy over the values. If the field is used in workflows, you'll have to change them to use the new field.

Regarding the history of the values: I would typically recommend to the delete the old field, but you don't have to do that - you can also just hide it from all relevant screens. In this case, the data would still be there, and you could look at it when needed.

For copying the values over: I've seen people use Automation rules for this, or do a CSV export, make changes to the CSV file, and re-import it.

Alternatively, if you're open to solutions from the Atlassian Marketplace, you'll have more options. I'll provide more information below.

Hope this helps,

Best,

Hannes

[Hannes Obweger - JXL for Jira]

... and to expand on my last point: If you're open to solutions from the Atlassian Marketplace, this would be easy to do with the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you'd do in e.g. Google Sheets or Excel. You can also bulk edit your fields, using copy/paste. This makes it very easy to copy values from one column (i.e., field) to another column/field, like so:

You can update any number of issues in one action, so you should be done with your work in no time. If an issue should still have multiple users set, the paste operation would fail for this issue with a meaningful error message.

I should also add that JXL can do much more than the above: From support for configurable issue hierarchies, to issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know!

[Darryl St_ Pierre]

Thanks @Hannes Obweger - JXL for Jira . While I like the functionality in your app, I'd prefer to handle this without the Marketplace.

I do appreciate the confirmation of how this needs to be addressed however!

[Mohamed Benziane · Accepted solution]

Hi,

you right, you will need to create a new field and verify where it is us to update rule, workflow. You can also try to use Automation to copy the current value in to the new field.