[MAGNOLIA-1106] workflow: comment for activation and comment for approving activation Created: 03/Oct/06 Updated: 23/Jan/13 Resolved: 23/Jun/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.0 RC3, 3.0 Final |
| Fix Version/s: | 3.6 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Stojan Peshov | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
irrelevant |
||
| 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)
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
Since m3 offers activation and approval steps, it would be nice if a user (editor for instance) that submits page for activation (notification) could enter a comment describing what his intentions, changes were. Both comments should be optional in order to preserve the current functionality. |
| Comments |
| Comment by Philipp Bracher [ 17/Nov/06 ] |
|
During rejection the supervisor can pass a comment (edit the item in the inbox). But this is not a good solution in the sense of usability. So the changes to made are:
In addition we need to pass a comment in the moment when the editor activates (starts the workflow). I don't know how we can solve this nicely, but we need to find a solution for that. |
| Comment by Philipp Bracher [ 23/Jun/08 ] |
|
If a user starts a workflow (activation) a comment dialog is shown |
| Comment by Boris Kraft [ 29/Jul/08 ] |
|
It seems to me that this comment box is always shown, even if we have no workflow enabled. This should not be the case, as without workflow, there is no use in an additional step. |
| Comment by Philipp Bracher [ 29/Jul/08 ] |
|
if you don't install the workflow module the dialog is not shown as expected. But once the module is installed the dialog appears no matter how the command chain is configured. To get rid of the dialog you have to change the tree configuration back to the default value. |