Datenbank #311
Add general dispute workflow
Status: | Neu | Start date: | ||
---|---|---|---|---|
Priority: | Dringend | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | Estimated time: | 5.00 h | |
Target version: | Repertoire 2) Testing phase II |
Description
There are different workflows right now
- Content.dispute (bool)
- Creation.state (on_approval, approved, rejected)
There should be a generalized workflow to handle all kinds of disputable objects.
We need a dispute object.
Related issues
History
#1 Updated by Alexander Blum almost 7 years ago
- Description updated (diff)
#2 Updated by Alexander Blum almost 7 years ago
- Description updated (diff)
#3 Updated by Alexander Blum almost 7 years ago
- Related to Konzept #333: Define the dispute workflow added
#4 Updated by Alexander Blum almost 7 years ago
- Related to deleted (Konzept #333: Define the dispute workflow)
#5 Updated by Alexander Blum almost 7 years ago
- Blocked by Konzept #333: Define the dispute workflow added
#6 Updated by Alexander Blum almost 7 years ago
- Blocks Webfrontend #334: Add claim interface added
#7 Updated by Sarah Stoffels about 6 years ago
- Assignee set to Sarah Stoffels
#8 Updated by Alexander Blum almost 6 years ago
- Estimated time changed from 2.00 to 5.00
#9 Updated by Alexander Blum about 5 years ago
- Assignee deleted (
Sarah Stoffels)
#10 Updated by Alexander Blum about 5 years ago
- Priority changed from Normal to Dringend
#11 Updated by Alexander Blum over 4 years ago
- Target version changed from 2) Testing phase II to Repertoire 2) Testing phase II
#12 Updated by Alexander Blum over 4 years ago
- Project changed from repertoire to collecting_society