[PUBTSKCONF-2] Allow auto-approve to exist as a subgroup of a configured groupMapping Created: 10/Nov/21 Updated: 26/Apr/23 Resolved: 11/Nov/21 |
|
| Status: | Closed |
| Project: | Publication Task Configuration |
| Component/s: | None |
| Affects Version/s: | 6.1 |
| Fix Version/s: | 6.1.1 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Richard Gange |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 4.75h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Description |
|
The use case is editors should still have to go through an approval step. Publishers should be able to skip the approval step. The idea is that auto-approve should not have to be directly configured on the task but indirectly through a groups within groups scheme. To be done:
|