...
The Issue Register Object can be added multiple times within one workflow. Further, the Issue Register Object will be either common to the workflow OR unique for the phase OR unique or incremental based on the organisation’s configurations.
If the Issue Register Object is common to the project workflow:
My Quick Update will display all issues which the user is responsible for in the current editable Issue Register object in the project workflow.
If the Issue Register Object is unique for the phase:
My Quick Update will display all issues which the user is responsible for in the current editable Issue Register object. Further, if there are any issues which the user is responsible for in any other Issue Register Object which is editable in the project workflow, those will also be displayed.
Issues will be first grouped by the ‘project’ they are linked to [Projects will be ordered by the project code] and then by the ‘phase’ [Phases will be ordered according to the order in the project workflow].
Issues under a particular phase will be ordered by the ‘Issue No’.
If the Issue Register Object is unique and incremental:
My Quick Update will display all issues which the user is responsible for in the current editable Issue Register Object. Further, if there are any issues which the user is responsible for in any other Issue Register object which is editable in the project workflow, those will also be displayed.
...
Which are linked to open projects.
From which you are the responsible officer.
From which you have view permission for the respective Issue Register object.
Which have not been resolved.
...
In order to edit issue actions, the relevant project should be opened.
...
Action No. – Displays the Action No. for the issue action. Not editable.
Action Title – Displays the Action Title for the issue action. Not editable.
Date Logged – Displays the Log Date for the issue action. Non-editable.
Date Resolved – Displays the Resolved Date for the issue action. Date Resolved will be enabled when the ‘Action Status’ is “Resolved”. Otherwise, it will be blank.
Status – Displays the Action Status for the issue action.
Comment – Displays the comment for the issue action . Editable.
Issue Register Object
...
My Quick Update will display all issue actions which you are responsible for in the current editable Issue Register object in the project workflow.
Issue actions are grouped by :
The ‘project’ which the issue actions are linked to [Projects will be ordered by the Project Code].
The ‘issue’ which the issue action is linked to [Issues will be ordered by the Issue No].
...
-The ‘phase’ which the corresponding issue register object is available in the workflow [Phases will be ordered according to the order in the project workflow].
3. The ‘issue’ which the issue action is linked to [Issues will be ordered by the Issue No].
...
Which are linked to open projects.
For which you are the responsible officer for.
For which you have view permission for the respective Issue Register object.
Which have not been resolved.
...
In order to edit issue decisions, the relevant project should be opened.
...
The ‘project’ which the issue decisions are linked to [Projects will be ordered by the Project Code].
The ‘issue’ which the issue decision is linked to [Issues will be ordered by the Issue No].
...
The ‘project’ which the issue decisions are linked to [Projects will be ordered by the project code]
The ‘phase’ which the corresponding issue register object is available in the workflow [Phases will be ordered according to the order in the project workflow].
The ‘issue’ which the issue decision is linked to [Issues will be ordered by the Issue No].
...
4. The ‘issue action’ which the issue decision is linked to [Issue actions will be ordered by the Action No].]
| Info |
|---|
Note: |
...
If the issue decision is linked to the issue “Issue 1” and to the issue action “Action 1”, then the corresponding issue decision will be grouped under “Issue: Issue 1”, “Action: Action 1”.
If the issue decision is linked to the issue “Issue 1”, but not linked to an issue action, then the corresponding issue decision will be grouped under “Issue: Issue 1”, “Action: Not Linked”.
If the issue decision is linked to the issue action “Action 1”, but not linked to an issue, then the corresponding issue decision will be grouped under “Issue: Not Linked”, “Action: Action 1”.
If the issue decision is not linked to an issue or an issue action, then the corresponding issue decision will be grouped under “Issue: Not Linked”, “Action: Not Linked”.
Issue decisions should be ordered by the ‘Decision NoNo’.’
iii. If the Issue Register object is unique and incremental:
...
The ‘project’ which the issue decisions are linked to [Projects will be ordered by the project code]
The ‘phase’ which the corresponding issue register object is available in the workflow [Phases will be ordered according to the order in the project workflow].
The ‘issue’ which the issue decision is linked to [Issues will be ordered by the Issue No].
...