... | @@ -21,13 +21,14 @@ As a result, JIRA tends to be used only for the issue title, brief description, |
... | @@ -21,13 +21,14 @@ As a result, JIRA tends to be used only for the issue title, brief description, |
|
|
|
|
|
See also:
|
|
See also:
|
|
|
|
|
|
* Issue #817
|
|
|
|
* [The future of JIRA](jira-to-gitlab-migration) - or "github vs gitlab"
|
|
* [The future of JIRA](jira-to-gitlab-migration) - or "github vs gitlab"
|
|
|
|
|
|
# Process / Roadmap
|
|
# Process / Roadmap
|
|
|
|
|
|
We have been reaching out to developers, users, partners, members to ask about what works and what can be improved. You can see the roadmap in #817 which includes bits on how the discussion evolved. Our plan is to come up with a final roadmap by February 2018 at the latest. While we have not made formal announcements about JIRA yet (as of December 2017), we have been documenting the process and raising awareness in various spaces/channels/lists/sprints/camps, gathering feedback as we go.
|
|
We have been reaching out to developers, users, partners, members to ask about what works and what can be improved. You can see the roadmap in #817 which includes bits on how the discussion evolved. Our plan is to come up with a final roadmap by February 2018 at the latest. While we have not made formal announcements about JIRA yet (as of December 2017), we have been documenting the process and raising awareness in various spaces/channels/lists/sprints/camps, gathering feedback as we go.
|
|
|
|
|
|
|
|
The roadmap is in: #817
|
|
|
|
|
|
# Feature requests & specs
|
|
# Feature requests & specs
|
|
|
|
|
|
Since December 2017, new projects have been created under the Development Team group in Gitlab:
|
|
Since December 2017, new projects have been created under the Development Team group in Gitlab:
|
... | | ... | |