Details
-
Suggestion
-
Resolution: Done
-
Not Evaluated
-
None
-
None
-
None
-
None
Description
We need a separate JIRA issue type for major items on the roadmap.
Task type | Purpose | Permissions | More details |
---|---|---|---|
Requirement | The item used to communicate the roadmap | In the first phase, creating these issues should be restricted to Nokians , later extended as defined in open governance. | Does not exists yet. The workflow is similar to internal requirement except that "researching" becomes "specifying", and the Schedulable and Scheduled states are combined to a state called "Specified". So the "longest" workflow is Open -> Specifying -> Specified -> In progress -> Implemented -> Verified. Other transitions exist similarly to internal requirement workflow |
No changes are needed to the workflows of these existing issues or sub-issues. However, we should verify that the permissions are as requested here.
Task type | Purpose | Permissions | More details |
---|---|---|---|
Suggestion | Suggestions from the public/roadmap input | open for anybody | No action required as we use the existing workflow and permission scheme for suggestions, suggestions may be converted/incorporated into new requirements -> PM task |
Change request | C/R against an existing requirement | In the first phase, restricted to Nokians, later extended as defined in open governance. | |
Subtasks | Used for detailed planning, if work is planned in this system. | Same as parent issue type | Enabled for Suggestions, Requirements, Tasks, Bugs |
The new Requirement issue type should be enabled in these projects:
- Nokia Qt SDK Installer
- Qt
- Qt Creator
- Qt Mobility
- Qt Quick Components
- Qt Simulator
- Qt Solutions
- Qt Visual Studio Add-in
- QtWebKit