How to show/hide the custom user assignee field based on custom checkbox field value?

Amruta Pelapkar
Contributor
February 14, 2021

Hello,

Is there any way to show/hide custom user assignee field based on custom checkbox field value?

2 answers

0 votes
Benito Picarelli
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 12, 2014

Hello Anthony,

After running this bulk change, did you have the chance to run a full locked re-index?

https://confluence.atlassian.com/display/JIRA/Re-Indexing+after+Major+Configuration+Changes

Please run this and let us know if the indexing of the issues bulk-changed appears correct.

Anthony Mastrean June 25, 2014

Thanks for the tip, Benito. I'm on an old JIRA and have to trigger the reindex manually, cross my fingers, and hope it comes back overnight :)

0 votes
Bruna Griebeler
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 11, 2014

Hi Anthony,

Thanks for sharing this experience with us. Indeed a user cannot be removed when it still has issues created on his username, so it's possible that there is, still something locking it.

I suggest you to check on your database for this user (nobody) and see where it is still set, specially on the tables related to issues such as jiraissue.

Here is the Jira Database Schema:

https://developer.atlassian.com/display/JIRADEV/Database+Schema#DatabaseSchema-IssueFields

PS: Instead of checking each table, creating a database dump and then analyzing it as text, should help on looking for this user in all tables at once.

Anthony Mastrean June 12, 2014

I'm certain that the user has no more tickets assigned. I bulk changed 1000s of tickets today. The fake-unassigned user's profile still shows all of these tickets! I just assigned a new ticket to the built-in unassigned and this fake-unassigned user's ticket count increased!

The problem seems to be in the username (field) or the assignee (search field). It's literally "unassigned" for both my user and the built-in user that JIRA uses for unassigned tickets.

Suggest an answer

Log in or Sign up to answer