How to replace custum field single choice with cascading custum field in jira project.

[Manoj]

Hi,

How to replace custum field single choice with cascading custum field in jira project. 

What would be the possible impact on existing tickets. 

[Hannes Obweger - JXL for Jira · Accepted solution]

Hi @Manoj 

just to add to Alan's answer, if you want to then copy the values from your "old" custom field to your "new" custom field, you may want to try JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing and inline-editing all your issue fields, including all custom fields. You can also edit your fields in bulk, using copy/paste, and simply copy values from one field to the other, like so:

I should add that the values of the old custom field and the new custom field need to be "compatible", but that's easy to sort out. It's also worth noting that JXL can do much more than the above: From quick sorting and filtering, to support for issue hierarchies, grouping, sum-ups, and conditional formatting. (Disclaimer: I work on JXL :)

Hope this helps,

Hannes

[Manoj]

Thanks Hannes, for the detailed explainations and its a new learning for me, will explore more onto this. 

I have a few more query, would you mind to guide, 

There is a project but now I need to add a new issue type, but have to use same workflow with additional status in work flow, 

For example issue type... Major Services is old one and new issue type is "Minor services' (which I have to create) once I create this, I have to add a status.. Sent for finance Manager approval, but if the value I put in custom field is greater 50k then it will go for department heads approval. 

Can you guide me about this, if you need any more details to understand the requirement, I will be Okay share. 

[Hannes Obweger - JXL for Jira]

If you want to do this as a one-time action, this would be easy with JXL; you can simply add your custom field to the table, perform column filtering to see only the issues with a value of 50K or greater, and then change the status of these issues using the same copy/paste bulk update as described above.

If you want to move issues to "Sent for finance Manager approval" on an ongoing basis - i.e., whenever the custom field value is changed - you may need Jira Automation.

Hope this helps,

- H

[Alan Stephenson · Accepted solution]

Hi

not recommended. It is better to create a new field. Fields can’t change from one type to another.

[Aditya Sastry · Accepted solution]

Hi,

Please do the following

1. Create a new cascading custom field.

2. Replace it with the single select field.

3. Using scriptrunner plugin copy the values from single select field to cascading field.

Thanks,
Aditya

[Manoj]

Hi Aditya, Thanks for your reply, I will be checking this in jira preprod First, however I have never worked on script runner plugins, as I am new to jira but getting good hold while exploring this community. 

I have a few more query, would you mind to guide, 

There is a project but now I need to add a new issue type, but have to use same workflow with additional status in work flow, 

For example issue type... Major Services is old one and new issue type is "Minor services' (which I have to create) once I create this, I have to add a status.. Sent for finance Manager approval, but if the value I put in custom field is greater 50k then it will go for department heads approval. 

Can you guide me about this, if you need any more details to understand the requirement, I will be Okay share. 

[Alan Stephenson]

Hi,

When you create a new issue type, depending on your how your workflow was created it may inherit the workflow you have defined "all issue types". Example: You can have one workflow for Story issue type and another workflow for Bug, Task, and yet a third workflow just for sub-task. Ideally it is better to try and keep workflows simple because it may confuse users when they are working on BOARD views trying to drag a issue from one column to another and the column they are trying to drag to isn't part of that issues' workflow.

As for your question above regarding what status based on what value is in the custom field, that may take some additional work in a script runner function or another add-on. You could build something like this:

If status in Needs Approval and custom field < 50K  then move ticket to Finance Manager Approval.

If status in Needs Approval and custom field > 50K then move ticket to Department Head. 

The way I would do is something like this:

Open -> Needs Approval -> Finance Manager -> continue with workflow process.....

and 

Open -> Needs Approval -> Department Head -> continue with workflow process

Since I don't have access to draw the workflow think of it as two options after Needs Approval. There is some automation which checks the validity of the custom field you have and this status (needs approval) is where the calculation / decision is made.

Not sure if it will work, but the concept sounds like this may work for your needs. 

-alan

[Manoj]

Thanks @Alan Stephenson I have created closely the way you had explained above. 

Just one thing, existing issue type has some script work done to auto fill the custom fields,when I update one custom field and the other relative custom field pick up the value

While other issue type created and workflow and schemas are linked into the new issue type but custom field behavior has changed, any idea where to check this in script behavior?