10.Requirements Analysis

1

Functionality to create sub-tasks for multi-object requests based on # of Object IDs selected for Jira applications outside of the Imaging app. Currently sub-tasks are based on # of object IDs x views, light type, etc. Artic would want to maintain that functionality for IMAGEREQ but enable multi-object requests for non-IMAGEREQ applications

OPEN

2

Functionality to tighten up the failure response of the Imaging app in the new multi-node environment based on the discussions with Artic

• Deletion of temporary files

• Responsibility to process the custom plugin logic has to be taken out of each node into a separate app

• Some kind of asynchronous processing has to be introduced

OPEN

3

Functionality to create sub-tasks using the Object (not in CITI) request forms based on comma separated list in the Object ID field x views, light type, etc. Seems like this would require CITI Request Type ID and CITI Request ID to be populated. wondering if we can do this via post function or something like that.

• At the time of creation there has to be an identifier in the request(in one of the fields of the JSD form) using which we can identify what kind of request it is and can take the required actions accordingly. Not sure if we can do this in Post functions as post function trigger is too late in the issue creation life cycle.

OPEN