Project

General

Custom queries



Profile

Actions

Defect #25806

open

Custom value from freshly disabled custom field in sub-project remains in issues list for parent project.

Added by Stephane Evr almost 8 years ago. Updated almost 8 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Create a project hierarchy such as:

 P1
  |
  P1.1

Create and Activate Issue Custom field C1 in Both projects.

Create an issue I1 in P1.1 with a value for field C1

Deactivate C1 in P1.1

Do not do any modification to I1

Go to P1 Issues view
Add C1 to selectedcolumns
Apply

Actual: Former value of C1 for I1 still shows
Expected: value of C1 for I1 shall be empty.

I know that if I save I1 after deactivating C1, the associated custom value for C1 will be erased, but the 'index' view should remain consistent with the 'show' view without having to manually perform a save.

#1

Updated by Mischa The Evil almost 8 years ago

  • Category set to Custom fields
  • Status changed from New to Confirmed
Actions

Also available in: Atom PDF