Startrekzky opened a new issue, #2535:
URL: https://github.com/apache/incubator-devlake/issues/2535

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   Allow users to define their own standard issue types and statuses when 
adding transformation rules for Jira boards at the 'create blueprint' flow.
   
   ### Use case
   
   ### Background 
   I have 10+ issue types: 
      - `epic` - indicating high-level goals
      - `story` - indicating feature requests
      - `subtask` - indicating technical tasks
      - `refactor` - indicating refactor or infrastructure work
      - `bug` - indicating bugs
      - `docs` indicating documentation work
      - `support` - indicating customer support work
      - etc. 
   
   ### User stories
   1. As a CTO or project manager, I want to see how high-level goals are 
executed in the daily work on a monthly or bi-monthly basis. Specifically, I 
want to see how much development resources (No. of issues or time spent on 
issues) are spent on each type of issue:
      - `Roadmap`: all `story` and `subtask` issues with an epic link, 
including `epic` issues and `subtasks` whose parent issues have an epic link.
      - `Unplanned`: all `story` and `subtask` issues without an epic link, not 
including `epic` issues or `subtasks` whose parent issues have an epic link.
      - `Infrastructure`: all `refactor` issues
      - `Support`: all `support` issues
      - `Other`: all issues that don't belong to the above 4 types.
   2. As a tech lead, I want to see how much development resources (No. of 
issues or time spent on issues) are spent on each type of issue on weekly 
retros to make better prioritization in the future. The issue types are:
      - `Feature`: all `Story` and `subtask`
      - `Bug`: all `bug`
      - `Infrastructure`: all `refactor`
      - `Documentation`: all `docs`
      - `Other`: all the rest of issues
   
   
    the standard type `INCIDENT`, but `docs`
   4. I have 8+ issue statuses
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to