JQL Issue Property caching problem

[Sebastian Rosenkranz]

Hi,

My team is developing a connect app, where we store data in the Jira issue properties, and now we want to make the issues filterable with these properties, so I looked into the connect module: jiraEntityProperties and I did it, so I tested it and it did work, kind of, thats where my problem comes in place. I created an issue, then I set the issue property and tested the jql, and it worked, then I tried to override the old property with a new one, that worked, and then I tested the jql again, and that didnt work, but it not only didnt work, it showed me my issue when I did the jql from before updating the issue property, so I thought maybe it gets cached or something, but after waiting round about 12h it still doesnt work correctly. So I wanted to ask if anyone else knows what the case is here, for you to understand it further here is my descriptor and what I have set the first time and the secound time for the issue as well as my jqls:

Descriptor “jiraEntityProperties” module:

jiraEntityProperties: [
    {
      key: 'test-entity-property',
      name: {
        value: 'test Index'
      },
      entityType: 'issue',
      keyConfigurations: [
        {
          propertyKey: SETTINGS.constants.PROPERTY_PREFIX + 'test',
          extractions: [
            {
              objectName: 'v',
              type: 'number',
              alias: 'version'
            },
            {
              objectName: 'items.userId',
              type: 'string',
              alias: 'userId'
            },
            {
              objectName: 'items.threads.threadId',
              type: 'string',
              alias: 'threadId'
            }
          ]
        }
      ]
    }
  ]

1. The First Issue Property I set after issue was created:

{
    "v": 3,
    "items": [
      {
        "userId": "ABC",
        "threads": [
          {
            "threadId": "123"
          }
        ]
      }
    ]
  }

2. JQL test that showed the correct issue for these jqls:

   1. threadId = “123”              OUTPUT: This Issue

   2. userId = “ABC”                OUTPUT: This Issue

   3. version = 3                      OUTPUT: This Issue

   4. userId = “Test”               OUTPUT: No Issue

   5. threadId = “Thread1”     OUTPUT: No issue

3. The Updated Issue Property with which I overwrote the first property on the exact same Issue:

{
    "v": 3,
    "items": [
      {
        "userId": "Test",
        "threads": [
          {
            "threadId": "Thread1"
          },
          {
            "threadId": "Thread2"
          }
        ]
    ]
  }

4. Second JQL tests which didnt show this issue:

   1. userId = “Test”                   OUTPUT: No issue

   2. threadId = “Thread1”         OUTPUT: No issue

   3. threadId = “Thread2”         OUTPUT: No issue

   4. threadId = “123”                 OUTPUT: This Issue

   5. userId = “ABC”                   OUTPUT: This Issue

   6. version = 3                         OUTPUT: This Issue

---

So I hoped this helped for your understanding of my problem, I just want to know why this is happening and how to fix this or if it is just a indexing/caching thing, where atlassian indexes it every 24h or something like that.

 I tried it the other way around too with a new issue, and it worked the exact same way, so I dont think my descriptor module is wrong 😕

PS: I also wrote the technical support about it, but maybe someone in the community knows this and answers a bit quicker :)

[Laura Campbell]

Hi @Sebastian Rosenkranz and welcome to Community

You'll find more help by asking this question on the Developer Community: https://community.developer.atlassian.com/