We should be able to make a unit inactive/disable a unit.
How it's done in the BZ database:
The information is stored in the table products in the field isactive.
If isactive = 1 (the default value) the unit is active.
If isactive = 0 (the default value) the unit is inactive/obsolete and it's NOT possible to create new cases/bugs for this unit.
The relevant parameter is:
is_open | boolean | true if the product is currently allowing bugs to be entered into it, false otherwise.
What we need:
Whether a property is active or not is a piece of information that we need to store in the MEFE <--- the source of truth for all information related to properties/units.
@nbiton How can this be done?
We also need to have a MEFE API that we can use to enable or disable a property in Unee-T
This issue tracks our progress to implement that API.
Requirement:
We should be able to make a unit inactive/disable a unit.
How it's done in the BZ database:
The information is stored in the table
productsin the fieldisactive. Ifisactive= 1 (the default value) the unit is active. Ifisactive= 0 (the default value) the unit is inactive/obsolete and it's NOT possible to create new cases/bugs for this unit.How it can be done with the BZ API:
BZ has a native REST API that we can use. See the documentation on the product update API for more details.
The relevant parameter is:
is_open| boolean | true if the product is currently allowing bugs to be entered into it, false otherwise.What we need:
Whether a property is active or not is a piece of information that we need to store in the MEFE <--- the source of truth for all information related to properties/units.
@nbiton How can this be done?
We also need to have a MEFE API that we can use to enable or disable a property in Unee-T
This issue tracks our progress to implement that API.