Hi,
I met a strenge case:
In Issue>Custom fields page (not in Field Configurations page), where we can create new fields, change field name, configure use contexts, and possibly give a default description for a field. I have a field which had a description, and I removed it, but the previous description is still displayed under the field on the configuration page itself (I do not talk about the Field configuration used in a Field configuration scheme). I don't know if it's a bug or there is a solution to it.
Has someone experienced the same problem ?
Thanks,
Xavier
Hi,
I just make a report to this case.
We would know where the old text of the field description is defined as we had no way to remove it with Jira admin tools.
We found that in our Jira data base ‘propertystring' table, there is the old text.
We removed the text with “update propertystring set propertyvalue='''' where id = <id>
and we restarted Jira.
Then the new text given in the field Description is displayed under the field name, and the old text has disappeared.
In all field configuration schemes the old text is still displayed as default text, but once removed, the new text is displayed instead (that was not the case before).
However, the question why the ‘propertystring' table contains the old string and why it had not been updated by new field description remains mysterious.
As it’s a single case and we already found a solution to it, in a common agreement with Jira support team, we would not take more time to study the original cause, and we could study it if a new case would be arised in future.
Regards,
Xavier
Hi @Xavier Tang
Just to make sure that I understand correctly... You removed the description on the Custom Field configuration level but when you Saved new settings the description is still there (on the Custom Field configuration) and cannot be removed or you removed it but it is still displayed as a description when field is viewed on the screen?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thank you for your question. Yes, exactly. This is the only case I met so far (no problem for other fields). It's special. I raised a bug ticket on Atlassian support, and they could not reproduce the case.
Regards,
Xavier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.