OpenConext / OpenConext/OpenConext-access

MVP Contractual part

Open
#724 5 comments 0 reactions 1 assignee View on GitHub

@oharsta is already working on this.

Since Sep 18, 2026.

MVP
Dominant language
JavaScript
Stars
4
Forks
0
Avg merge
1d 14h
Merged PRs (30d)
22

Description

For MVP, implement a form with following items. Users are able to fill out this form only once. After submit, a QTC ticket will be created and ticket must be assigned to 'klantsupport group' (SURF Klantsupport [SURF-GROUP]).

Position of the agreement changes from App level, to Org level:

Figma designs
Prototype: https://www.figma.com/proto/81StIVqfOKfwhWVjx7Ew81/SURF-Access?node-id=9904-3028&viewport=142%2C-519%2C0.66&t=eofJhVN8a2ZkNIqC-8&scaling=contain&content-scaling=responsive&page-id=9684%3A52896&hide-ui=1
Design: https://www.figma.com/design/81StIVqfOKfwhWVjx7Ew81/SURF-Access?node-id=9904-3028&t=0Tx6d9GpdVd5KZ93-1

When the contract has been signed, this should be visible in the UI. Perhaps for now, we can create a button in the 'system' tab to toggle that the contract has been signed or not.

  • Naam van de Service Provider:

  • De naam van de persoon die de overeenkomst bij de Service Provider tekent:

  • Aanhef van de persoon die de overeenkomst bij de Service Provider tekent:

  • De functie (bijvoorbeeld Directeur) van de persoon die de overeenkomst bij de Service Provider tekent:

  • Vestigingsadres van de organisatie:

  • Telefoonnummer contractnemer:

  • E-mailadres contractnemer:

  • Name of the Service Provider:

  • Name of the person from the Service Provider who will sign the agreement:

  • Proper way of addressing the person who signs the agreement:

  • Title (e.g., "CEO") of the person who signs the agreement:

  • Address of the organization:

  • Telephone number of contact for the contract at the Service Provider:

  • Email address of contact to send the contract to at the Service Provider:

Business rules

  • Applications created by Institution Org Admins do not have to do contractual part (implicit that they approved)
  • Applications created by Institution Org Members need to be approved by the Institution Org Admin (Institution Org Admin needs to get a notification on creation? [NOT MVP])
  • Applications created by External Org Admin/member always need to finish the contractual part
  • Org guests have been invited for a Institiution or External app, they don't have any business with contractual part, see https://github.com/OpenConext/OpenConext-access/issues/840
  • App members don't have any business with contractual part (same logic as previous item)

Ticket requirements:
Project: Quote to Cash (QTC)
Issue Type: Service Request
Summary: SURF Access Aansluitovereenkomst
Service: SURF Access (now: SURFconext)
Reporter: SURFconext Second Line [SURF-GROUP]
Assignee: SURF Klantsupport [SURF-GROUP]

Jira requirements
The issue type ID for 'Service Request' in the QTC project is 11300.

A tip is, if you know of an existing issue in that project, view it from the API, and you can get the IDs for the issue type, custom fields, etc. Just use https://servicedesk.surf.nl/jira/rest/api/2/issue/${existing issue key}, For exmple https://sd-jira-staging.surf.nl/jira/browse/QTC-1017

To get a list of IDs available at issue creation for the Service Request issue type, you can hit this endpoint: https://servicedesk.surf.nl/jira/rest/api/2/issue/createmeta/QTC/issuetypes/11300

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.