[#JRA-6851] Allow more than one custom field context to be associated with the same project but different issue types

JIRA

Allow more than one custom field context to be associated with the same project but different issue types

Created: 01/Jun/05 02:53 AM Updated: 30/May/08 11:24 AM

Component/s:

Custom Fields

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Participants:	Anton Mazkovoi [Atlassian], Jeff Turner [Atlassian], Olle Friman, Richard THIBAULT, Sverrir Tynes and Todd Warrington
Since last comment:	18 weeks, 4 days ago
Support reference count:	3
Labels:

Description

« Hide

In the custom field configuration context, it is not possible to choose a project if it has already been associated to another configuration context of the same custom field. For instance, it is not possible to make the following associations:

Task, project1, configuration context 1
Task, project2, configuration context 2
Bug, project1, configuration context 3
Bug, project2, configuration context 4

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Todd Warrington added a comment - 15/Dec/05 01:57 PM

I have the same problem. I need to set up different configurations of a custom field for different issues in the same project.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 12/May/06 12:17 AM

It sounds like a bug to me (can't see why it shouldn't be possible?).

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 08/Sep/06 02:35 AM

The current behaviour is indeed by design.

Only 1 Custom Field Context can be associated with a project. The context can optionally specify one or more issue types. If no issue types are specified the custom field will be available to all issues in that project. If one or more issue types have been specified in the context the custom field will be available to issues in that project for the chosen issue types. Issues in the project of a different issue type will not have the custom field at all.

Note, that it is possible to have a Custom Field Context that applies to no project and some issue types. This context will affect issues for which there is no project specific Custom Field Context.

Implementing the functionality proposed in this issue is a bit of a technical challenge and is not on our road map of date.

Please leave this issue as an improvement.

Thanks,
Anton

[ Permlink | « Hide ]

Olle Friman added a comment - 15/May/08 01:48 AM

Growing with Jira will sooner or later end up that you need ability to add different context per issue type and project. I have now a short term workaround. I am worried this issue will not be completed in the close future. It has not been touched an almost 2 years.
I am voting and hope there will be some action.
Thanks /Olle

[ Permlink | « Hide ]

Sverrir Tynes added a comment - 30/May/08 11:24 AM

I have just voted for this issue as it will solve a problem I´m having when working with context.
I would also be able to select components or versions from the projects selected in the context.