Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Highest
Fix Version/s: 4.2.2, Bugfix Release
Affects Version/s: 4.1
Component/s: None
Labels:
- affects-server

Introduced in Version:
4.01
Bug Fix Policy:
View Atlassian Server bug fix policy

When you change the name of a priority, status, resolution or status we do not call refresh for their caches and they become stale.
This affects places that use the Objects rather than the genericValues.
The changes are only reflected once you restart the system.

See AbstractEditConstant.doExecute()
This should either call an abstract method that just clears that Constants cache or it could just call DefaultConstantManager.refresh()

causes

JRASERVER-22219 In Workflow used status is not updated after renaming the status itself

Closed

details

JRASERVER-23197 remove note about restart when renaming a Priority (when JRA-23196 is fixed in 4.2.2)

Closed

is duplicated by

JRASERVER-22637 Issue status modifications do not reflect in workflow steps and issue navigator search terms

Closed

JRASERVER-22749 Priority and issue type strings hardcoded all over the place

Closed

JRASERVER-23200 Issue Types are not sorted alphabitically anymore after renaming any issue type

Closed

JRASERVER-23613 priority level names don't update

Closed

is related to

JRASERVER-24146 After workflow scheme migration, issue moved to a newly added status are not readable

Closed

(1 is duplicated by, 1 is related to)

Assignee:: Peter Leschev

Reporter:: Nick Menere [Atlassian] (Inactive)

Votes:: 2 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 06/Dec/2010 11:47 PM

Updated:: 12/Sep/2019 6:35 AM

Resolved:: 04/Jan/2011 2:58 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates