search

devsecopsmaturitymodel / DevSecOps-MaturityModel

GNU General Public License v3.0
484 stars 279 forks source link

State or Tag for "Not yet assessed" #241

Closed LittlePrimate closed 2 months ago

LittlePrimate commented 1 year ago

I'd like to throw a possible improvement in here for discussion: differentiation between features that you do not have and features that were not (yet) evaluated.

Currently the only way I see is checking whether you wrote something in e.g. the "Evidence" field, which can make it hard to get started again when you for some reason took a break during you assessment.

Options might be a "todo"-label (which would make the yaml searchable and could be translated into some kind of symbol on the chart - @ptechofficial was thinking about some kind of yellow exclamation mark symbol as a first idea) or simply a third state. I think the third state might make the whole thing more messy, especially because you can no longer simply check the Implementation Chart. Additional question would be whether this label/state/whatever should then be automatically applied to all categories or if it's something the user has to add manually. In theory starting in "Todo" would actually make sense in my mind because you either want to anyways manually remove levels you do not want to assess or you can leave them in the Todo-state to signal that, while these fields are still white, it does not mean that your team/organisation is not doing this, you actually just never assessed it.

Any thoughts on this?

ivareri commented 1 year ago

Having a tri-state (Not assessed, implemented, not implemented) would be useful to keep track of progress. Esp. if you need to pause in the middle of an assessment and return to it days, or weeks, later.

During some assessments I've also been missing a "Not applicable" state.

wurstbrot commented 7 months ago

With the current "tags", you can reach such a status. But to do it is difficult I think because it is not very handy.

jdsmithit commented 7 months ago

Hey I also want "Not Applicable" as a state which can be updated in the UI :D

github-actions[bot] commented 2 months ago

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be closed automatically in one week if no further activity occurs.

github-actions[bot] commented 2 months ago

This issue was closed because it has been stalled for 7 days with no activity.