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

As a JIRA Administrator I want to kill user session

    XMLWordPrintable

Details

    • 140
    • 6
    • Hide
      Atlassian Update – 28 June 2023

      Hi everyone,

      Thank you for taking the time to file and comment on this issue. We've reviewed it and agreed it’s a priority for us to resolve. Our engineers have already started working on the issue.

      Please continue watching this ticket for future updates and changes in the timeline that may impact your work.

      Andrzej Kotas

      Jira DC Product Manager

      Show
      Atlassian Update – 28 June 2023 Hi everyone, Thank you for taking the time to file and comment on this issue. We've reviewed it and agreed it’s a priority for us to resolve. Our engineers have already started working on the issue. Please continue watching this ticket for future updates and changes in the timeline that may impact your work. Andrzej Kotas Jira DC Product Manager
    • 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.

    Description

      Problem Definition

      Currently, there's no way to kill a user session if a user is found to be calling requests which could slow down the overall performance of JIRA application.

      Suggested Solution

      Add an administration utility to end particular user session.

      Workaround

      How to force all users of Atlassian on-prem products to re-authenticate their sessions on the browser

      Attachments

        Issue Links

          Activity

            People

              eaec06bb454d Andrzej Kotas
              syong@atlassian.com Sean Yong
              Votes:
              220 Vote for this issue
              Watchers:
              114 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: