Issue Details (XML | Word | Printable)

Key: JRA-12671
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Andreas Knecht [Atlassian]
Reporter: Nick Menere [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Unassociated calculated fields are displayed on confirmation pages of Move and Convert issue, even when not in context

Created: 04/May/07 12:06 AM   Updated: 09/May/07 02:40 AM
Component/s: Custom Fields, Custom Fields (new types), Issue Fields
Affects Version/s: None
Fix Version/s: 3.9.1

Time Tracking:
Not Specified

Participants: Andreas Knecht [Atlassian] and Nick Menere [Atlassian]
Since last comment: 1 year, 17 weeks, 4 days ago
Resolution Date: 09/May/07 02:40 AM
Labels:


 Description  « Hide
If a field has been hidden or is not in a context for an issue, it will be displayed on the confirmation page for move or convert issue, if the system thinks it has a value.

The system will think it has a value if it is calculated field or if it has a value in the database. (i.e. the field used to be in context or not hidden, was given a value and then removed from context or hidden).

When retrieving removed fields, we must find the intersection of all hidden fields for the target context and all displayed fields in the current context.

This should be done in DefaultIssueConversionService.getRemovedFields()



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Andreas Knecht [Atlassian] added a comment - 09/May/07 02:40 AM
Issue conversion and move issue operations now correctly check for the existence of a fieldLayoutItem in the original issue and make sure the original field isn't hidden.