Confirming Revised Issues


The member who is going to confirm revised output documents should check them whether they have been revised appropriately based on issue contents.
Status of issue should be updated to “Confirmed” or “Remanded” based on revised contents.
Here is described how to check revised issues.


Flow of Confirming Revised Issues

The flow of confirming the revised issues and updating issue status is as follows:

Confirming Revised Issues

  1. Select [Tile View] or [Grid View] from the [View] menu to show the issue list.
  2. You can filter issues with filtering function if you need. Please see “Confirming Issue Contents” for filtering function.
  3. Move the cursor to the target issue and click [Detail] button to show the issue detail view.
  4. Click [Reported/Revised] button to check reported and revised contents.


Updating Issue Status as “Confirmed”

  1. If there is no problem with the revised contents, click [Status] icon on the [Detail] screen or the [Properties] pane to update the status from “Revised”115005341547_03.png  to “Confirmed”115005341547_04.png. Issue is closed when its status is set to be “Confirmed”. If you have a comment in the revised contents, enter it in the [Comment] tab.

Remanding Issue

  1. Click [Remanded]115005341547_02.png button and return the issue to the member for revising if there is anything wrong in the revised contents.
    Status will be updated from “Revised”115005341547_03.png to “Not Revised”115005341547_05.png.
    * If the options of “Revise Plan Decided”115005341547_06.png and “Revise Plan Approved”115005341547_07.png are included in the status, it wiil be updated to “Revise Plan Approved”115005341547_07.png.


  2. Enter the reason for remanding the issue in the [Reason of Remand] tab on the [Detail] screen. You can easily find remanded issues at a glance as the [Remanded] button is highlighted.
    The button is also highlighted on the issue list, so the members for revising are also able to get priority of issues.



Was this article helpful?
0 out of 0 found this helpful