Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-73182

documentation of Vulnerability fixes for LTS versions

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Documentation - All
    • None
    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      For almost every vulnerability Issue there is often the problem that it has been closed because it has been fixed, but the fix version is a release version beyond the LTS version. Because the Issue is closed no one knows if there will be a LTS fix coming or not. And if not, why? Or if, when it will be shipped.

      Could you make this more transparent? A lot of people are starting otherwise asking in the comment for a LTS fix, without any response. The handling for LTS fixes of vulnerabilities is very diffuse. Sometimes there is no statement for a LTS fix at all, so you hope when upgrading the minor version of a LTS will solve it, but you never know.
      This is not helpful to keep/build the trust in the application.

      Suggested Solution

      You could extend your workflow in order to illustrate there is still bugfixing going on for a LTS, by another status, for example...

      Workaround

      None

            [JRASERVER-73182] documentation of Vulnerability fixes for LTS versions

            No work has yet been logged on this issue.

              500376cac1e1 Daria Shatsylo (Inactive)
              408c4e8c446d Michael Aglas
              Votes:
              61 Vote for this issue
              Watchers:
              46 Start watching this issue

                Created:
                Updated: