Details
-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
None
-
2
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Scenario
JRA-34394 was implemented as an upgrade task to fix incorrect watch counts. However, the upgrade task triggers a reindexing that reindexes all of the available issues in the database, thus slows down the upgrade process.
Suggestion
Only the affected issues (with incorrect watch counts) should be reindexed.
Attachments
Issue Links
- derived from
-
JRASERVER-34394 Watch count gets out of sync when cloning issues
- Closed
- is incorporated by
-
JRASERVER-59194 Upgrade tasks should trigger foreground reindexing instead of background reindexing
- Gathering Interest
- is superseded by
-
JRASERVER-47052 Provide option to disable Index task during upgrade.
- Gathering Interest
- relates to
-
JRACLOUD-59195 UpgradeTask_Build64001.java should only reindex affected issues
- Closed
-
JRASERVER-47044 Jira reindex triggered during upgrade doesn't indicate progress in log
- Gathering Interest