How to use text (not JSON) entity properties in JQL?

[Yuriy Marchenko]

Hi everyone,

We've been using some entity (project, issue) properties, having text values in there worked perfectly fine, the conditions in the descriptor work fine, the REST API, etc.

Now the time has come to add a webhook for issue updates and we need to use the entity properties we have (with text inside, not JSON) to filter out once we don't care about.

The problem is the documentation explains how to index the properties with JSON values...

Does anyone happen to know how to index such fields or is there a way to use them for JQL search without indexing?

Any information helps, thank you!

[Shayne _Atlassian_ · Accepted solution]

1. That's correct.
2. The XML backup will migrate all information stored within JIRA's database, which includes everything you mentioned, though the user data may be a little bit of a grey area depending on whether or not you've configured your instance of JIRA to connect to an LDAP server.
3. Some other files you may want to backup before upgrading can be found in our documentation for Important Directories and Files under the 'JIRA Installation Directory' heading. These are the more commonly modified files in a JIRA installation.

I'd also recommend establishing a staging environment so you can run through the upgrade to make sure everything works as expected before you proceed with upgrading your live/production environment. Once you've upgraded the staging environment, spend a little time running through the more commonly used areas of JIRA to make sure that things are looking good.

I hope that helps!

[Paulo Hennig]

Hello Steven,

Questions 1 & 2 are "Yes". About question 3, if you have attachments enabled, all files attached to JIRA issues are stored in the data\attachments directory (not in the database), so XML backup won't save your attachments. Please, have a read here