-
Suggestion
-
Resolution: Duplicate
-
None
If an user is a project administrator, he can also see the message recommending a re-indexing to be performed. Once this user is not a JIRA administrator, he cannot do what the message asks for and it gets a confusing situation. For this reason, this message should only be displayed to JIRA administrators.
- duplicates
-
JRASERVER-20543 A link to Re-Indexing is visible to users even if they are not sys admin
-
- Closed
-
[JRASERVER-22047] Do not show the recommendation to perform a re-index to non JIRA administrators
I raised a support call for this (JSP-80777) and I got a workaround for now.... pasted below
After spend few hours on digging into the JIRA files, apparently this is non JSP/VM controlled. Its coded at JIRA source code, inside DefaultReindexMessageManager.java below:
public synchronized String getMessage(final User user) { if (propertiesReference.get().exists(PS_KEY_USER)) { final String userName = propertiesReference.get().getString(PS_KEY_USER); final String i18nTaskKey = propertiesReference.get().getString(PS_KEY_TASK); final Date time = propertiesReference.get().getDate(PS_KEY_TIME); final I18nHelper i18n = i18nFactory.getInstance(user); final OutlookDate outlookDate = outlookDateManager.getOutlookDate(i18n.getLocale()); String userFullName = userFormatManager.formatUser(userName, FullNameUserFormat.TYPE, "fullName"); String i18nTask = i18n.getText(i18nTaskKey); String timeString = outlookDate.formatDMYHMS(time); StringBuilder message = new StringBuilder(); message.append("<p>").append(i18n.getText("admin.notifications.task.requires.reindex", userFullName, i18nTask, timeString)); message.append("<p>").append(i18n.getText("admin.notifications.reindex.now", "<a href='" + getContextPath() + "/secure/admin/jira/IndexAdmin.jspa'>", "</a>")); message.append("<p>").append(i18n.getText("admin.notifications.complete.all.changes")); return message.toString(); } return null; }
This will required you to modify source code and you will need to build a JIRA patch to your production instance which is not recommended and NOT support by Atlassian Support as stated in our Support Policy.
Hence I recommend you another method which is to modify the warning message. You can find these message in parameters below in JiraWebActionSupport.propertie inside your language package.
########################
# Admin notifications
########################
admin.notifications.task.requires.reindex={0} made configuration changes in section ''{1}'' at {2}. It is recommended that you perform a re-index. For more information, please click the Help icon.
admin.notifications.reindex.now=To perform the re-index now, please go to the ''{0}Indexing{1}'' section.
admin.notifications.complete.all.changes=Note: So that you only have to re-index once, you may wish to complete any other configuration changes before performing the re-index.
You can refer to document below for more information on how to customizing it:
+1.
This is a bug not an improvement. Why show a message to a user & give them a link to a feature they can't use.
Users are reporting this & it appears Jira is broken to them.
Eric Rawlins
added a comment - I have received several complaints from users in my company that are project administrators but not system administrators. They see this prompt and don't know what they are supposed to do with it when, in fact, there is nothing they can do.
I would suggest that since they are receiving a prompt to reindex when they have no privledges to do such a reindex this is really a bug, not an improvement.
Eric Rawlins
added a comment - I have received several complaints from users in my company that are project administrators but not system administrators. They see this prompt and don't know what they are supposed to do with it when, in fact, there is nothing they can do.
I would suggest that since they are receiving a prompt to reindex when they have no privledges to do such a reindex this is really a bug, not an improvement. 
Yes, this is confusing to our users as well. Can something be done about this? Rather than rebuilding jira ourselves, I would rather get a fix from Atlassian for this.