Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to disable option value of a Project Specific custom field

Orawan Sittakom
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 16, 2015

I tried to search this problem in Google but I find nothing about this.

We found some option value of a Project Specific custom field unable to be disabled. When we select "disabled" and then click on Update button, it seem the process cannot be ended (see a screenshot). After refreshing the page, that option value is still enabled. 

Have you ever found this issue before? Please also advise how to fix it. 

Thanks.

image2015-9-17 10:41:10.png

2 answers

0 votes
Holger Schimanski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 17, 2015

What version of Project Specific Select Field are you using? And are you using custom field type Project Specific Select Field (simple)? https://marketplace.atlassian.com/plugins/jira.plugin.projectspecificselectfield.jpssf

Then I guess you are running in the same problem as described here, which was recently reported by another user. https://bitbucket.org/hski/projectspecificselectfield-public/issues/46

This problem is related to some special characters. In your case "/" in the option value.

I will provide a bugfix release soon.

Best regards
Holger

Orawan Sittakom
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 17, 2015

Thank you very much! It's correct. The custom field type that we are using, is Project Specific Select Field (simple) and the option value that we tried to disable is "DCO Move CVS/SVN" (that having "/"). So that means, currently there is no solution to fix it and I have to wait for a bug fix release. Is that right? To do data integrity check or JIRA restarting, does not help, right?

Holger Schimanski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2015

Yes, data integrity check and JIRA restart will not help. It is a bug in the plugin, which I am going to resolve. Meanwhile you can disable the value via SQL. Please see https://bitbucket.org/hski/projectspecificselectfield-public/wiki/Home in section SQL API.

Orawan Sittakom
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 20, 2015

Thank you! it worked.

0 votes
Pilar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 16, 2015

It is possible that the project specific custom field is used by several projects. So any enabling / disabling of options will make those options enabled/disabled for all projects. Sometimes if the option is used by other projects then it may be difficult to disable them.

What i suggest you to try is create a new custom field context for your project, and then enable/disable options. Hopefully it should work then.

Pilar

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events