Reporting Bugs and raising Feature Requests
Check our JIRA Issue Tracker issue tracker in order to see if your planned contribution is new.
If you find a feature or bug has already been reported, please don’t let this deter you from reporting it yourself. Doing so will help prioritise issues.
If you can contribute to fix or add the feature, please read our Contributors guides. If you are planning on contributing a feature or bug fix, it is still advisable to discuss it with us first, as it may be something that is already being worked on and we would want to avoid wasted effort.
Generally please provide the following information:
- Which version of SEEK are you using? / URL of the SEEK
- Do you want to contribute to the development? When/where?
- Do you want to contribute design or testing work?
- Can you point us to resources, like e.g. source code or tools related to your proposal?
When raising a feature request please try and provide as much information as possible. Provide a clear description of the feature request from a user perspective - outlining the problem and what the user is trying to achieve, rather than describing only a solution.
When raising a bug or problem, please provide any details that would help to reproduce it. An numbered list of steps is often the most useful. In some cases a screenshot may be helpful.
What happens next?
Within 2 work days you will receive a receipt, stating that and who will be processing your request.
Within 7 work days we will contact you to discuss the feature in more detail; whether it is something you can contribute and how we can help; or details about how the feature fits in with our other priorities and timeline.
Usually, an issue will be raised in our JIRA Issue Tracker and you will be provided with a link to follow its progress.
If the feature gets developed by ourselves, we will keep in touch with you and ask for feedback and final testing.