For a while, one of my apps has been storing a count in an issue property. I exposed this value via property extractions so it is searchable via JQL. Recently, I get more and more requests from customers who also want to also “see” and report the issue property value (e.g. in search results in the issue navigator) instead of just using it in JQL.
Does anyone have some suggestions on what’s the best way to do this?
I have researched a few options but none of them seems really appealing to me (yet):
Use an issue field
Disadvantages are that I cannot use the existing entity property value as field value and it seems not possible to have a read-only field.
Create a custom field
The same problem as with the issue field (cannot use the existing entity property value) however, there seems to be a read-only custom field type.
Generally, I would prefer a solution that re-uses the existing issue property value so I don’t have to maintain it in two places but unfortunately, I couldn’t find a way to do this.
Has anyone faced a similar situation before and can give some hints on how they solved it?