Change Jira ticket types

Aperta
#1,144 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
backend

Direzione di ricerca

Start by tracing how Access Dashboard creates Jira tickets and where it currently assigns the 'SSI Change' type; the issue does not name files or tests. Map each listed action to its proposed Jira type, then check how existing ticket creation tests verify those types. Done means all five actions create the corresponding types from the table.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

New Feature Request

Summary

For clarity, we'll introduce jira ticket types that match its purpose. When Access dashboard creates a ticket, from the ticket type it must be clear what's the purpose of the ticket.

Problem: What is the pain point? (e.g., "Users cannot filter results by date.")
Now, only 'SSI Change' ticket type is used.

Value: Why should we build this? (e.g., "Improves data accessibility for
power users.")
Since automations in Jira are also dependent on unique ticket types, this is necessary. @oharsta it would be nice if Manage has the same terminology.

Proposed Solution

Action in Access Dashboard Manage reference Jira ticket type Jira Veld
Activate an app ActivationRequest SAD ActivationRequest @andre klaver
Request activation for app ActivationRequest SAD ActivationRequest @andre klaver
Deactivation app DeactivationRequest SAD DeactivationRequest @andre klaver
Make change to production app ChangeRequest SAD ChangeRequest @andre klaver
Publish connection ProductionRequest SAD ProductionRequest @andre klaver
  • Action: Describe the logic or flow change.
  • Design: [Link to Figma/Screenshots]
  • Impact: Does this affect existing APIs or UI components?

Testing and QA

Describe how to verify and test this change.

Test Environment and Setup
  1. Point to [URL/Branch]
  2. Use account with [Role/Permissions]
Test Checklist
  • Happy Path: Feature works as intended under normal conditions.
  • Edge Case: [Describe specific test item]
  • Validation: [Describe specific test item]
  • UI/UX: Verified layout across screen sizes.

Extra Information

Add any other context, related issues, or technical notes here.

Lingua principale
Java
Stelle
4
Fork
0
Merge medio
1g 2h
PR unite (30g)
39

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenConext/OpenConext-access

Tutte le issue di OpenConext/OpenConext-access

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.