...
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 |
| ||||||||
| 2 | Changed the date format | Bug |
| |||||||||
| 3 | Custom Field values should have precedence. | Feature |
| |||||||||
| 4 | Out Of Office feature | Feature | Done the POC |
| ||||||||
| 5 | Issue links between same and different issue type | Feature |
| |||||||||
| 6 | Add provision to configure group to make control access of app | Feature |
| |||||||||
| 7 | Project key validation | Bug |
| |||||||||
| 8 | Weblink Implementation in Template | Feature |
|
Requirement | Description | Estimated time to complete the task | |
|---|---|---|---|
| 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. |