This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
No labels!
There aren’t any labels for this repository quite yet.
The change implied or requested by this issue will to be implemented
All work related to this issue has been done
This issue or pull request already exists
A human being is working on this problem
The described facts are not correct and therefore no change is required.
All work related to this issue has been done and must be reviewed by the reporter or a team member
The team needs to discuss how to deal with the issue's request
It is unclear to the team if the requested enhancement can be usefull for a wider usergroup
Feedback by the user who has filed this issue is required to continue the work on this issue
The behavior described is intended as it is and is exactly as it should be.
This issue mainly focuses or has impact on the performance of jQA
Changes or enhancements to the documentation are necessary for this issue
This issue mainly focuses on how jQA is build or which libraries are used
This issue mainly focuses on the performance of jQA
This issue mainly focuses or has impact on the security of jQA
Software shows incorrect behavior or delivers incorrect results
Enhancement of the functionality of the software
A question asked by a user who needs help
A piece of work that must be done, but does not represent a noticeable change for the user
You can’t perform that action at this time.