Welcome to our new Issue Tracking System!

This site is powered by the open-source product OpenProject that has replaced our previous Jira solution. We can ensure all your data are stored locally with us.

• Don't worry, all the issues are still here, and an old link to a Jira issue will redirect you directly to the same issue in our new system. If the link doesn't match the issue exactly, it will at least bring you to this site.
• You can still log in with your existing username and password.
• Use this link to register.
• Check this video to see how to report an issue with our new support site. There is also this document on our docs.
• There are some new terms you might need to get used to. For example, what was previously referred to as an "issue" will now be a "work package". There are various types of work packages you are already familiar with such as bugs, features, etc.

If you encounter any technical problems with our new site, please contact us at: admin@evolveum.com

Please, do not report security vulnerability here!

Read how to report security vulnerability responsibly.

Issue workflow

1. Create an issue with all the necessary information (how to reproduce it, logs, screenshots, error messages), affected versions and subscriber information. Please, don't fill in Assignee and Fix version/s. If unsure, leave the fields empty.
2. If SLA applies, the issue will be responded to – ideally accepted as Confirmed, or moved to More info needed if there is not enough information to act upon it. In special cases, when more investigation is needed from Evolveum, Labels field might be set to "support".
3. After fixing, the issue will be Resolved.
4. It is advisable for the author to check the solution (using a snapshot build) and confirm the fix with the status change to Verified.
5. If the ends up in any other final status it can be reopened if good reason is provided.

Users can't modify the issue info, but comments and attachments can be added later as well.