Closed mahalakshme closed 6 months ago
@vinayvenu / @arjunk review this
The values do not seem to belong to a single dimension and 'category' is too generic. Defeats the purpose of having this as a JSON. Suggest we break them down to more specific dimensions so that it is more extensible in the future. i.e. have something like:
{
"dataClassification": "prod", < prod | test >
"usage": "prototype" < demo | prototype | none > etc
}
or simplify this to having a set of well-defined tags of which one or many can be applied to an org.
@vinayvenu I prefer in keeping them as one category or jusy may be with a different label. You can check the above comment and reply with your opinion.
@mahalakshme I agree with@1t5j0y here. Support looks for prod orgs that are active. Development needs uat orgs that are active, but may also need a backup. Website needs all orgs that have ever gone to prod but needs a separate category for those who have discontinued.
Bunching all of these into a single "category" feels wrong.
@vinayvenu @1t5j0y Once a card moves to Ready lane, it is upto the developer and what the team feels how they want to implement. I am responsible until moving a card to Ready lane. So feel free to decide.
Since this is (mostly) for internal usage and relies heavily on us maintaining this metadata correctly, I'm leaning towards the tags solution since it should serve the purpose and not require us to drill down into the possible dimensions. Also, saves us effort on changes to webapp UI to manage this metadata if/when we introduce new dimensions or values for dimensions. The tags solution does not cater to the other use case of uat-prod org linkage but that is probably best done via a more robust linking mechanism.
@1t5j0y I remember we discussed about tags solution only initially, since that is what I had analysed first. And based on the inputs from product team and sales team, I moved it to this solution which is the current AC. We also discussed the reasons for the same in the last call. I am not sure how to go about this now, the team can decide.
yes that is expected. implementation and support teams will be mark them UAT etc incrementally.
Need:
Acceptance criteria:
When creating an org as super admin, I should be able to set the category for the org. The allowed categories are prod, UAT, prototype, temporary. Display it immediately below 'Username suffix' field. Similar dropdown as Account. The label name for the field is 'Category'.
Show the field in Create mode, when clicked on Show and when clicked on Edit.
The field is mandatory, hence when not set, show the error message as 'Please select a category' like below:
Also display the field to the right of 'Username suffix' here.
Technical:
Since more such fields will come up, store category in a JSON field, so that it is extendable for later. This is based on what was discussed during Monday discussion. Feel free to change it based on what is best.
Out of scope: