[Bug] Assignee field in jira-search contains a name when it should be empty/unassigned

[jhqv]

Describe the bug "Assignee" column in jira-search table contains incorrect values. Since I started using this awesome plugin, I've noticed that the values in the "assignee" column are frequently wrong. It seems like the tickets that are unassigned are given somewhat random names of assignees from other tickets.

After taking the screenshots attached to this ticket, I performed a force-reload of Obsidian. After that, some of the tickets got a correct assignee (unassigned) but others in the table still had incorrect values.

Query:

jira-search  
query: creator in (currentUser()) AND created >= -30d order by created DESC
limit: 15

Expected behavior I expect the "assignee" column to match the truth from the JIRA server.

Screenshots As you can see, in the JIRA interface only three tickets are assigned, but in the Obsidian JIRA table all tickets are assigned. It seems like the assignee field is "sticky".

Plugin version and platform

• Version: 1.52.0
• [x] Obsidian Mac v1.1.16

[ehmsen]

I have the same issue. I have debugged it using the console, and it seems as if the "assignee" field in the json response for an issue is null, then the plugin does not reset that field but keeps the value from the previous issue in the list return from Jira. Hence if the Jira returns a list of issues, then the plugin behaves as follows:

• First issue in the list returned from Jira: If the "assignee" field in the json response is set to a json object containing "displayName" "John Doe", then the plugin displays "John Doe" in the table presented in Obsidian.
• Second issue in the list returned from Jira: If the "assignee" field is null (not an object), thenb the plugin displays "John Doe" in the table presented in Obsidian. The correct value here is to display "Unassigned".

[cbruyndoncx]

I came to the same conclusion and asks chatGPT for fix. I think the proposed fix is correct, but probably not as elegant as reinitializing the variable correctly for each row, but I have no obsidian plugin skills in order to test this. I have this issue on several empty or unassigned fields in my table. https://chat.openai.com/share/f311dbbd-ceda-4e0d-9c41-f6a732b49952

[marc0l92]

this is a duplicate of #78

[marc0l92]

Thanks for reporting this issue, the fix has been released in version 1.53.0

[cbruyndoncx]

Thanks for fixing, but something is out-of-sync I think in the versions. The plugin upgrade failed, I uninstalled and then the install fails too. I think v1.54.0 is defined, but not actually released.

[marc0l92]

@cbruyndoncx are you able to update the plugin now?