Issue Details (XML | Word | Printable)

Key: JRA-10237
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Sam Chang [Atlassian]
Reporter: Cecile Gorin
Votes: 0
Watchers: 0
Operations

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

Customfields belonging to specific projects are shown when those projects are selected

Created: 22/May/06 08:54 AM   Updated: 30/Jul/06 07:37 PM
Component/s: Custom Fields
Affects Version/s: 3.5
Fix Version/s: 3.6.3

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Cecile Gorin, Sam Chang [Atlassian] and Scott Farquhar [Atlassian]
Since last comment: 2 years, 13 weeks, 5 days ago
Resolution Date: 10/Jul/06 12:45 AM
Labels:


 Description  « Hide
I have created 2 customfields, each one belonging to a specific project.
When I perform a search on those 2 projects, I can see the 2 customfields in the search form.
The problem is that if I select a value for customfield number 1, the search returns results in the project number 1 only. I have no results for the project number 2.
In addition, if I select a value for Customfield number 1 and a value for Customfield number 2, I have 0 result.

IMHO:

When selecting multiple projects, customfields not being configured for the context (ie available for the 2 projects) shouldn't be visible in the search form.

OR

When performing the search, Jira should search results with a "OR" condition whereas a "AND" condition: search issues in project 1, project2 where customfield1=value or customfield2=value
In this case, we will have results.

Thanks,
Cécile



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] added a comment - 23/May/06 09:24 AM
Cecile,

Thanks for the input. I completely agree.

I'm closing this issue as duplicate, as there are other issues which deal with 'OR' conditions, and improving the scoping of fields for the issue navigator.

Cheers,
Scott


Sam Chang [Atlassian] added a comment - 10/Jul/06 12:45 AM
The fix for JRA-10276 also addresses this issue - only custom fields applicable to the context selected through the navigator will be displayed.