Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Parallel signing #18

Open
5 tasks
Tracked by #78
TheTechArch opened this issue Mar 16, 2019 · 0 comments
Open
5 tasks
Tracked by #78

Implement Parallel signing #18

TheTechArch opened this issue Mar 16, 2019 · 0 comments
Labels
area/process area/signing Epic feature-complete In relation to A2 and June 2023 kind/product-feature kind/user-story Used for issues that describes functionality for our users. org/brg Issues relevant for Brønnøysundregistrene. org/digdir Issues relevant for Digitaliseringsdirektoratet org/ssb Issues relevant for Statistisk sentralbyrå. status/draft Status: When you create an issue before you have enough info to properly describe the issue. ux Needs some love from a UX resource

Comments

@TheTechArch
Copy link
Member

TheTechArch commented Mar 16, 2019

Description

In some scenarios, there is a need for requiring that multiple users need to sign the same task.

The minimum number of signatures needs to be defined by the app developer and it needs to define who is authorized to sign it.

Orgs can define who can sign based on roles or giving input direct to instance. (that trigger delegation of app rights)

Consideration

  • Requires instance delegation in place before this can be implemented

Specification task

  • Analyse how are app delegated to users

Acceptance criteria

  • It is possible to define the minimum number of signatures on a signing task
  • It is possible to define who is authorized to sign by roles
  • It is possible to define who is authorized to sign when instance is instansiated

Tasks

  1. feature-complete kind/feature-request org/brg org/krt status/draft
  2. status/triage
  3. status/triage
  4. status/triage
  5. status/triage

Tasks

  • Verify that this issue is labeled and written correctly (remove unused stuff, add missing stuff, verify tasks). DoP.
  • Documentation (if relevant)
  • Test / QA (if relevant)
@TheTechArch TheTechArch added area/process kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Mar 16, 2019
@lvbachmann lvbachmann added the org/ssb Issues relevant for Statistisk sentralbyrå. label Apr 24, 2020
@lvbachmann lvbachmann added Epic org/digdir Issues relevant for Digitaliseringsdirektoratet labels Oct 6, 2021
@FinnurO FinnurO added the org/brg Issues relevant for Brønnøysundregistrene. label Jan 19, 2022
@TheTechArch TheTechArch transferred this issue from Altinn/altinn-studio Feb 17, 2022
@FinnurO FinnurO added the feature-complete In relation to A2 and June 2023 label Dec 7, 2022
@RonnyB71 RonnyB71 added the ux Needs some love from a UX resource label Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/process area/signing Epic feature-complete In relation to A2 and June 2023 kind/product-feature kind/user-story Used for issues that describes functionality for our users. org/brg Issues relevant for Brønnøysundregistrene. org/digdir Issues relevant for Digitaliseringsdirektoratet org/ssb Issues relevant for Statistisk sentralbyrå. status/draft Status: When you create an issue before you have enough info to properly describe the issue. ux Needs some love from a UX resource
Projects
Status: No status
Status: No status
Status: No status
Development

No branches or pull requests

4 participants