Scope of work
§ Develop an app to select Makino projects based on Template for Contract review ( common across all Order ) and Stock MC w/ Options
§ User should be able to select the custom fields and option/value from the project template during the order creation screen
§ Auto-create issues/tasks in the destination project with Stock MC w/ Options and contract review task
§ Feature to select project templates, Destination projects, and issue types.
§ On creation of the Makino project, confluence space and a page tree structure to be auto-created and Confluence pages should be auto-linked to the respective Makino project issues/task
§ Users should be able to attach documents to the confluence from Jira and see their versions on the issue/task view screen
§ Configure the template for Contract review and Stock MC w/ Options
Programmatic Approach
We recognize that all our customers are unique with regards to their processes and availability and therefore, by nature of our services, we remain flexible to accommodate the Makino team in a way that works for all parties. With that said, below we have described what we envision this engagement to look like and how we will work toward the program goals.
Assumptions
All the required fields should be mapped to Issue Type screen
If any changes are made in the “template” the changes will be reflected to newly created projects ONLY and not the existing project.
Customer will provide list of all the fields and issue types (Any field type inclusion other than Text /Number, Single select and multi-select fields will impact the deliverable timelines).
Link between Jira Cloud and Confluence Server is already in place
While uploading the document, user will mention label of the attachment as an optional parameter
No document search feature from Jira Cloud. User will need to go to Confluence Server to search the document.
Customer will host and maintain the infrastructure for custom app
Empyra will provide infrastructure and hardware requirements
Work Breakdown Structure for Implementation
Sl No | Main Task | Description |
1 | Project Template |
|
1.1 | Create a projects (Template project for Contract review and Stock MC w/ Options) | Create a projects (Template project for Contract review and Stock MC w/ Options) along with issue type , tasks and custom fields |
2 | App Dev | |
2.1 | Contract Review |
|
2.1.1 | UI Design | Develop the UI for Contract Review Screen. Provision for the user to select the custom field and enter values |
2.1.2 | Business Logic | Development of custom logic to read the configuration, custom fields , issues and create the same in target project |
2.1.2 | Modular Testing(Contract Review Testing) | Testing the module |
3.1 | SO Process |
|
3.1.1 | UI Design | Develop the UI for SO Screen. Provision for the user to templates |
3.1.2 | Business Logic | Development of custom logic to read the configuration, custom fields , issues and create the same in target project |
3.1.3 | Modular Testing ( SO Process) | Testing the module ( SO Process) |
3.1.4 | Regression ( 1,2,3) | Test the Contract Review and SO collectively |
3.1.5 | Logger Implementation | Implement Logger to log any issues during the Contract Review / SO process |
3.1.6 | Build Process Pipeline for Queue | Development of Logic to push the request to queue to process the creation of project/configuration/issues |
4.1 | Confluence(Panel Creation for file upload) |
|
4.1.1 | Confluence(UI Design) | Development of UI to upload the attachment and add labels |
4.1.2 | Confluence(Business Logic) | Develop logic to push the attachment in confluence |
4.1.3 | Confluence(Testing) | Testing the module |
5 | UAT | |
5.1 | Testing by the business user | User Acceptance testing end-to end process |
6 | Production Deployment | |
6.1 | Deployment of application to production environment | Deployment of application to production environment |
7 | Documentation | Document the implementation details |
8 | Hyper-care | Observe the process/instance for a week |
Timelines
Tasks/Features Added in UAT Phase
Tasks | Type | Status | Jira Issue | |
|---|---|---|---|---|
| 1 | Copying the custom field values from parent to subtask once all the issues being created from APP | Feature | Done | AP-2289 - Getting issue details... STATUS |
| 2 | Changed the date format | Bug | AP-2307 - Getting issue details... STATUS | |
| 3 | Custom Field values should have precedence. | Feature | AP-2227 - Getting issue details... STATUS | |
| 4 | Out Of Office feature | Feature | Done the POC | AP-2370 - Getting issue details... STATUS |
| 5 | Issue links between same and different issue type | Feature | AP-2289 - Getting issue details... STATUS | |
| 6 | Add provision to configure group to make control access of app | Feature | AP-2303 - Getting issue details... STATUS | |
| 7 | Project key validation | Bug | AP-2287 - Getting issue details... STATUS | |
| 8 | Weblink Implementation in Template | Feature | AP-2288 - Getting issue details... STATUS |
Requirement | Description | Start Date | End Date | Estimated time to complete the task for both order management and contract review | Estimated time to complete the task for order management | |
|---|---|---|---|---|---|---|
| 1 | New template idea for project creation | Instead of having multiple project templates with each full of dozens of tasks, we would like to create a single master template with all possible tasks for any type of machine project. We would also create template definitions or mappings for which tasks are associated with which templates. For the project creation process we would then pick a template like normal, but instead of copying an entire project it will refer to the mapping and only copy over the tasks associated with that template. This prevents us from keeping multiple templates in sync. For future maintenance we would be able to update the master project, and the template definitions. |
Total-48h |
Total-28h | ||
| 2 | Script for copy over parent issue field values to subtask. | Need to copy the parent issue field values to subtask. | 8h(including testing) |