Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

My Issues

By default, this section will display issues:

  • Which are linked to open projects.

  • For which you are the responsible officer.

  • For which you have view permission to respective Issue Register object which have not been resolved.

Inline Quick update will display below given information for each issue:

  • Issue No. – Displays the Issue No for the issue. Non-editable.

  • Issue Title – Displays the Issue Title for the issue. Non-editable.

  • Date Logged – Displays the Log Date for the issue. Non-editable.

  • Date Resolved – Displays the Resolved Date for the issue. Date Resolved will be enabled when the ‘Project Issue Status’ is “Resolved”. Otherwise, it will be blank.

  • Status – Displays the Project Issue Status for the issue.

  • Comment – Displays the Resolution /Recommendation for the issue.

Issue Register Object

  • 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.

My Issues Filters

The following filters will be available for My Issues:

  • Issue No. – A text box which allows to type in the issue no and search for the issue. This is a key word search and therefore by entering a part of the issue no. you will be able to filter out all issues that contain the typed characters anywhere in the issue no.

  • Issue Title – A text box which allows you to type in the issue title and search for the issue. This is a key word search and therefore, by entering a part of the title, you will be able to filter out all issues that contain the typed characters anywhere in the title.

  • Date Logged – A date picker which allows you to specify a From and To date and filter out all issues which appear outside the given date range.

  • Status – A dropdown lists of all issue statuses defined in the system. Selecting a status would display only the issues of the selected status. Defaults to “Show All".

  • Hide Resolved Issues – Ticking this would exclude all resolved issues from the list. Ticked by default.

My Issue Actions

By default, this section will display issue actions:

  • 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.

Inline Quick Update will display below given information for each issue action.

  • 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

Issue Register object can be added multiple times within one workflow. Further, 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.

  1. If the Issue Register object is common to the project workflow:

    1. My Quick Update will display all issue actions which you are responsible for in the current editable Issue Register object in the project workflow.

    2. Issue actions are grouped by :

      1. The ‘project’ which the issue actions are linked to [Projects will be ordered by the Project Code].

      2. The ‘issue’ which the issue action is linked to [Issues will be ordered by the Issue No].

Note: If an issue action is not linked to an issue, then that issue action should be shown under the group “Issue: Not linked”. The “Issue: Not Linked” group should be shown after all issue actions linked to any issue are displayed under the project.

iii. Issue actions are ordered by the ‘Action No’.

2. If the Issue Register Object is unique for the phase:

  • My Quick Update will display all issue actions which you are responsible for in the current editable Issue Register object. Further, if there are any issue actions which you are responsible for in any other Issue Register object which is editable in the project workflow, those will also be displayed.

  • Issue actions should be grouped by:
    - The ‘project’ which the issue actions 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].

3. The ‘issue’ which the issue action is linked to [Issues will be ordered by the Issue No].

Note: If an issue action is not linked to an issue, then that issue action should be shown under the group “Issue: Not linked”. The “Issue: Not Linked” group should be shown after all issue actions linked to any issue are displayed under the phase.

-Issue actions are ordered by the ‘Action No’.

My Issue Actions Filters

The following filters are available for My Issue Actions:

  • Issue No. – A text box which allows you to type in the issue no and search for the issue actions linked to the issues with the issue no entered.

  • Issue Title – A text box which allows you to type in the issue title and search for the issue actions linked to the issues with the issue title entered.

  • Action No – A text box which allows you to type in the issue action no and search for the issue action.

  • Action Title – A text box which allows you to type in the action title and search for the issue action.

  • Date Logged – A date picker which allows you to specify a From and To date and filter out all issue actions which fall outside the given date range.

  • Status – A dropdown lists of all issue action statuses defined in the system. Selecting a status will display only the issue actions of selected status. Defaults to “Show All".

  • Hide Resolved Issue Actions – Ticking this will exclude all resolved issue actions from the list.

My Issue Decisions

By default, this section will display issue decisions:

  • 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.

Inline Quick Update will display the below given information for each issue decision:

  • Decision No. – Displays the Decision No for the issue decision. Non-editable.

  • Decision Title – Displays the Decision Title for the issue decision. Non-editable.

  • Date Logged – Displays the Log Date for the issue decision. Non-editable.

  • Date Resolved – Displays the Resolved Date for the issue decision. Date Resolved will be enabled when the ‘Decision Status’ is “Resolved”. Otherwise, it will be blank.

  • Status – Displays the Decision Status for the issue decision.

  • Comment – Displays the comment for the issue decision.

Issue Register Object and Groupings 

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. 

i.  If the Issue Register object is common to the project workflow:

  • My Quick Update will display all issue decisions which you are responsible for in the current editable Issue Register object in the project workflow. 

  • Issue decisions should be grouped by:

  1. The ‘project’ which the issue decisions are linked to [Projects will be ordered by the Project Code].

  2. The ‘issue’ which the issue decision is linked to [Issues will be ordered by the Issue No].

Notes:

  • If an issue decision is not linked to an issue, then that issue decision should be shown under the group “Issue: Not linked”. The “Issue: Not Linked” group should be shown after all issue decisions linked to any issue are displayed under the project.

  • Under the ‘Issue: Not Linked’ grouping, there can be issue decisions which are linked to an issue action OR issue decisions which are not linked to any issue action.

3. The ‘issue action’ which the issue decision is linked to [Issue actions will be ordered by the Action No]. 

Notes:
 If an issue decision is not linked to an issue action, then that issue decision should be shown under the group “Action: Not linked”. The “Action: Not Linked” group should be shown after issue decisions linked to any issue action are displayed under the project.

 Example for groupings:

  • 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 No’.

ii.    If the Issue Register Object is unique for the phase: 

  • My Quick Update will display all issue decisions which the user is responsible for in the current editable Issue Register object. Further, if there are any issue decisions which you are responsible for in any other Issue Register object which is editable in the project workflow, those will also be displayed.

  • Issue decisions should be grouped by:

  1. The ‘project’ which the issue decisions are linked to [Projects will be ordered by the project code]

  2. 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 decision is linked to [Issues will be ordered by the Issue No].

Notes: 

  • If an issue decision is not linked to an issue, then that issue decision should be shown under the group “Issue: Not linked”. The “Issue: Not Linked” group should be shown after all issue decisions linked to any issue are displayed under the project.

  • Under the ‘Issue: Not Linked’ grouping, there can be issue decisions which are linked to an issue action OR issue decisions which are not linked to any issue action.

4. The ‘issue action’ which the issue decision is linked to [Issue actions will be ordered by the Action No].

Note:
If an issue decision is not linked to an issue action, then that issue decision should be shown under the group “Action: Not linked”. The “Action: Not Linked” group should be shown after issue decisions linked to any issue action are displayed under the project.

 Example for groupings: 

  • 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 No’. 

iii.  If the Issue Register object is unique and incremental: 

  • My Quick Update will display all issue decisions which you are responsible for in the current editable Issue Register object. Further, if there are any issue decisions which the user is responsible for in any other Issue Register object which is editable in the project workflow, those will also be displayed. 

  • Issue decisions should be grouped by:

  1. The ‘project’ which the issue decisions are linked to [Projects will be ordered by the project code].

  2. 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 decision is linked to [Issues will be ordered by the Issue No].

Notes:

  • If an issue decision is not linked to an issue, then that issue decision should be shown under the group “Issue: Not linked”. The “Issue: Not Linked” group should be shown after all issue decisions linked to any issue are displayed under the project.

  • Under the ‘Issue: Not Linked’ grouping, there can be issue decisions which are linked to an issue action OR issue decisions which are not linked to any issue action. 

4. The ‘issue action’ which the issue decision is linked to [Issue actions will be ordered by the Action No].

Note:

  • If an issue decision is not linked to an issue action, then that issue decision should be shown under the group “Action: Not linked”. The “Action: Not Linked” group should be shown after issue decisions linked to any issue action are displayed under the project.

Example for groupings: 

  • 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 No.’

  • No labels