[MGNLWORKFLOW-271] Bulk actions don't make sense Created: 28/Aug/14 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | 5.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Isabelle Dubach | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
In Assigned and Resolved categories, for example, I can bulk-assign them to me. This doesn't make sense - if they're assigned, I don't want to assign them again, and if they're resolved, I don't need to act on them at all (except for deletion, which is not possible, see issue http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-270. It would be be great if bulk actions would be relevant to the context. |
| Comments |
| Comment by Florian Fuchs [ 03/Jul/15 ] |
|
It would be reasonable to "unassign" tasks at this position. |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |