• Priority of bug reports


    bonienl

    Very often I see people marking their issue as "urgent" because it has impact on the operation of their system.

     

    Please consider carefully when to use the "urgent" priority. Using this level implies a serious bug affecting a large group of people.

    Make sure it is not related to the specific set up of your system. At minimum the issue must be reproduceable in safe mode.

     

    Any issue marked as "urgent" gets high attention at Limetech, but this gives a lot more burdon to investigate.

    If uncertain start with marking as "minor", if it turns out to be a serious issue its priority can always be raised.

     

    • Like 1



    User Feedback

    Recommended Comments



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.