Issue tracker

Our Jira issue tracker can be found here.

This is where you should go if you want to stay up to date with the Adaptyst development in a greater technical detail than through our blog. All feature suggestions and bugs are also submitted there as long as they are related to Adaptyst, Adaptyst Analyser, and/or one of the Adaptyst-team-made modules.

You don’t have to sign up to view issues and comments. Moreover, if you want to contribute there (e.g. by filing a bug) or view full information about our current workflows at CERN, logging in is simplified as much as possible:

If you’re affiliated with CERN, you can use your usual credentials.
If you have no links to CERN, you can use your private e-mail address, a GitHub/Apple/Google/social account, or an institutional account through eduGAIN. In case it’s your first time accessing CERN Jira, you need to subscribe here first (free of charge).

The research and development work by us at CERN is organised in scrum-based sprints. More details can be found here. You can follow sprints by signing up to CERN Jira or checking out a corresponding thread in the forum (a currently-ongoing sprint is pinned in the General category).

Each issue can have one of these states:

Backlog: not scheduled in a currently-ongoing sprint.
To do: scheduled in a currently-ongoing sprint, but no work has begun yet.
In progress: the work is being carried out at the moment.
On hold: the work is being carried out in general, but it is not scheduled in a currently-ongoing sprint.
Waiting for third party: waiting for an input from another person/group at CERN.
Waiting for external: waiting for an input from a non-CERN person (e.g. a collaborator or an external contributor like you). We need to stress here that voluntary contributors never have any commitments towards us and are perfectly allowed to leave at any time: this is absolutely fine for us, but we’ll appreciate letting us know in this case so that we can update our planning.
Done: completed.

Visibility of issues

Some issues may not be visible for everyone due to either being too internal-specific (e.g. tasks requested by or for CERN LHC experiments) or confidentiality reasons (e.g. security vulnerabilities).

If you have permissions such as a CERN affiliation, you should log in before consulting the issue tracker.

Please rest assured though that if any hidden issues result in changes to Adaptyst, Adaptyst Analyser, or Adaptyst-team-made modules, the changes will be public and properly explained. The software itself will also stay open-source, especially once external contributions are present as we don’t have any CLAs in place (this is on purpose).

Same authentication for the issue tracker and forum

Once you log in to CERN Jira, you can reuse the same account for the Adaptyst forum. Similarly, if you have already signed up to the forum, you can reuse your account for CERN Jira (remember to subscribe here first in case you’re not affiliated with CERN, this is free of charge).

Installation

Outreach