We are changing the way we track issues raised by the Alfresco Community. Currently, anyone can either raise issues in Github or the ALF project in JIRA (https://issues.alfresco.com/jira/projects/ALF/summary). Going forward, we will only use Github for externally raised issues and code contributions.
Alfresco is in the process of migrating their on-premise JIRA instance to cloud, and we’re taking this as an opportunity to change the way we collaborate with external contributors. This shouldn’t have any impact on your access as open projects, such as MNT and ALF - these will continue to be available. If a ticket is not marked as internal, you will be able to access it regardless of having an account.
The timeline for the change is October 31st. After that, issues.alfresco.com will be made read-only and eventually decommissioned. The URL for the tickets will change, e.g. https://issues.alfresco.com/jira/browse/MNT-0001 will become https://alfresco.atlassian.net/MNT-0001. Once we finish the migration and back the data up, we will redirect the links to ease the transition.
We realize that we have many repositories on Github and that it can be challenging to identify the correct place to raise issues. To combat this, we have created a new repository “Collaborating with Alfresco” (https://github.com/Alfresco/collaborating-with-alfresco) which serves as a “catch-all”. Raise issues here if you are unsure of the correct repository, and we will route them into the appropriate repository.
These changes are all unimportant if we don’t fix the issues raised in Github. We are working with the delivery teams on how to better visualise, manage and eventually resolve the issues. We are working on boards in Github to show the tickets by product and also on integration between Github and JIRA (we still need the JIRA tickets to get the work done internally).
Finally, we are experimenting with this, so all feedback is welcome.
