How to expose issue property value as issue field?

custom-field
properties
jira-cloud

#1

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):

  1. 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.
  2. 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?


#2

Hi,

Yes. We ended with a code syncing both issue property and custom field, so it is a solution from your point #2.

We did not find anything better, unfortunately :frowning:

Cheers,
Jack


#3

Thanks for your reply @jack! That’s a pity, and I am surprised options seem to be still so limited in this area. I will do some more research to see how other apps do this. In this post, @dmeyer recommended not to use custom fields if not for personal use.

I wouldn’t recommend a custom field unless you’re building the app for personal use only


#4

@jack I talked to dev support regarding this issue and as a result there is now this feature request: https://ecosystem.atlassian.net/browse/ACJIRA-1631

Please upvote and ask your co-workers to upvote. Would be good if we could gain some attention on that.

Cheers!


#5

Voted and asked colleagues to do the same.

Thanks @tbinna!