Add Notifications for Data Safeguard Breaches in Jira Data Center

XMLWordPrintable

      It would be really helpful if Jira Data Center could notify users when they’re about to breach or have already breached data safeguards—similar to what’s already available in Jira Cloud.
      In Cloud, users get real-time pop-up alerts when they hit limits like the number of comments on an issue.
      There are also clear error messages through the API (e.g. 413 Content Too Large) and tools for admins to monitor these limits via log entries.

      Right now, Jira Data Center doesn’t seem to have anything like this, and it causes a lot of problems. Users don’t know there’s an issue until something breaks, and admins have no easy way to track limits or prevent problems ahead of time.

      Additionally the current safeguard alert system relays on email which can cause issues. If users could clearly see how often an account is making total requests they would better self regulate. We unfortunately cannot show users alternatives such as Grafana reports for several reasons.

      What I’m Suggesting:

      1. Add API & User pop up to Data center
          • Note: The user pop-up exists in DC (introduced in V9.0), but only for the single safeguard (Comments), this also does have the API controls to produce an Error Code of 400 Bad Request and includes a response message of "issue already reached maximum number of allowed comments and you can't add more"
        • Show a clear message when someone is approaching or has gone over a data limit (See linked Confluence Page for examples from Cloud). 
        • Include link to help article about what they need to do next (e.g.,split data across multiple issues).
      1. Account metrics on /secure/ViewProfile.jspa
        • Show calls made from this profile in last 24h / last 7d easily viewable by UI or API call
        • Highlight banner style alert on User profile page if rate limit or safeguard is breached. This could also improve data security by highlighting abnormally large data requests.

            Assignee:
            Unassigned
            Reporter:
            Keith
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: