Bug 1328629 - Add exclude rule for CFs visibility
Summary: Add exclude rule for CFs visibility
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Bugzilla
Classification: Community
Component: Administration
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-19 22:38 UTC by Jeff Fearn 🐞
Modified: 2019-01-24 00:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-24 00:26:09 UTC


Attachments (Terms of Use)

Description Jeff Fearn 🐞 2016-04-19 22:38:05 UTC
Description of problem:
Currently if a CF is set at the classification level then every product in that classification sees them.

This is fine when the classification all works the same way, but the community and internal classifications are a lot of unrelated teams and what different CFs available.

Currently he alternative is to do *all* CFs at the product level which woul be an enormous time sink and fragile.

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. Set a CF on at the classification level
2. Try and disable it for your product

Actual results:
Your product does have the unwanted CF.

Expected results:
Your product does not have the unwanted CF.

Additional info:
Two ways I can see to do this.

1: Add a product level control to select/deselct  classification and global CFs.

2: Allow editfields.cgi have multiple "Field only appears when" options.

Comment 1 Jeff Fearn 🐞 2018-03-13 06:35:58 UTC
It'll be simpler to just add a single exclude option.

Comment 2 Jeff Fearn 🐞 2019-01-24 00:26:09 UTC
In preparation for entering maintenance mode we are closing bugs that are unlikely to be scheduled in maintenance sprints.


Note You need to log in before you can comment on or make changes to this bug.