Support organization with DTAP features on platform (Development, Testing, Acceptance, Production)

Description of the limitation and why it is relevant to address

As an organization I want to ensure that the user is informed of the state and maturity of an application so that a high standard can be maintained with regards to calculating and producing results. This should not come to the detriment of hindering engineers to develop and share their developments.

I think this is relevant for the VIKTOR platform because it will continue to grow with features specific to engineering.

Submitter proposed design (optional)

Suggestions are:

  • Allow for apps to have tags “Development”, “Testing”, “Acceptance”, “Production”, which can only be changed by different individuals assigned to do that task. E.g. developer can switch from “Development” to “testing”, a tester can change from “Testing” to “Acceptance”, etc. or similar.
  • Be transparent in the individuals that were responsible in the different phases.
  • Inform the developer on criteria such as writing tests, coverage, so they can improve their skills and knowledge over time.

Current workarounds

Current workarounds would include having check lists that administrators need to enforce before giving the app a workspace. This is limiting as versions can be bumped to newer versions (refer to Pinning a version of an application to a workspace).

Other approaches would be to use the labels that are available, but also with the same limitations.

Requested by

Darren L.

This is also discussed with @Rutger

Received this reply as well:

Building trust and confidence in apps is tricky. How do you manage expectations (as not all apps are always production ready apps)? - Aaron G.

@pieter.bieghs and co. are interested, and want to participate in the conversation.