Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    JRASERVER-78795Ongoing recurring SLA field
  2. Suggestion
    JRASERVER-78794Incident Status Sub- Status
  3. Suggestion
    JRASERVER-69078Add a CAPTCHA validation to the "Contact Site Administrators" form
  4. Suggestion
    JRASERVER-76113Allow better scheduling in Data Pipeline
  5. Suggestion
    JRASERVER-78092Add better error handling for specific URL so it doesn't expose source code
  6. Suggestion
    JRASERVER-72546Allow editing of Jira Scheduled Jobs
  7. Suggestion
    JRASERVER-65071All clients need this: Notify blocked issues when blocker resolved
  8. Suggestion
    JRASERVER-4665Need to persist Mail Queue Items
  9. Suggestion
    JRASERVER-23498recycle bin for jira projects
  10. Suggestion
    JRASERVER-39511Change Date/time format on a per project basis
  11. Suggestion
    JRASERVER-67549Sort STATUSES alphabetically
  12. Suggestion
    JRASERVER-67787Incoming mail handler: Use project key in subject to select project for new issue
  13. Suggestion
    JRASERVER-70006Jira should not go into read-only mode when the license limit is exceeded
  14. Suggestion
    JRASERVER-74204Improve Jira issue type hierarchy
  15. Suggestion
    JRASERVER-38806Support throttling to handle Google SMTP error 454 4.7.0 Too many login attempts, please try again later.
  16. Suggestion
    JRASERVER-68068Add Exchange Web Services (EWS) to Jira
  17. Suggestion
    JRASERVER-72820'Atlassian Gateway' for Data Center products
  18. Suggestion
    JRASERVER-71721Extent the DC node list with node status
  19. Suggestion
    JRASERVER-62128Data Center offering for JIRA Core
  20. Suggestion
    JRASERVER-65032Issues in Epic list - show Story points next to all Stories
  21. Suggestion
    JRASERVER-72757Lack of a Permalink feature in the new view in Jira 8.17 and later
  22. Suggestion
    JRASERVER-71452Logs for bulk changes
  23. Suggestion
    JRASERVER-36892Add support for distributed object store via Amazon S3 API for storing JIRA attachments
  24. Suggestion
    JRASERVER-59453Ability to Change Default Permission Scheme
  25. Suggestion
    JRASERVER-78769Filter is not available under issue selector for users when linking an issue in the create screen
  26. Suggestion
    JRASERVER-73057Huge data in AO_733371_EVENT_PARAMETER has impact on undo space of Oracle DB
  27. Suggestion
    JRASERVER-5006Allow users to watch a project
  28. Suggestion
    JRASERVER-20094Cannot change link type after creating.
  29. Suggestion
    JRASERVER-19443"Distinct" qualifier in JQL
  30. Suggestion
    JRASERVER-77948Support and bundle SQL Server JDBC version 12.2 for future Jira 9.12 LTS releases
  31. Suggestion
    JRASERVER-38378Integrate Bamboo with Openshift
  32. Suggestion
    JRASERVER-45280Add JQL search bar gadget to dashboard
  33. Suggestion
    JRASERVER-64645Customer request for more control on user CSV import access
  34. Suggestion
    JRASERVER-67673Support Java Cryptography Extension required for Secure connections with TLS v 1.1 and v 1.2
  35. Suggestion
    JRASERVER-69808PDF autorotate or Manual rotate on Atlassian JIRA - Plugins - File viewer plugin
  36. Suggestion
    JRASERVER-70323Add the status of the issue on the notification email
  37. Suggestion
    JRASERVER-70549As a Jira Admin I would like to print cards using Avery Label templates.
  38. Suggestion
    JRASERVER-70843Can we update expensive queries?
  39. Suggestion
    JRASERVER-71684Customizable Customfield name for project
  40. Suggestion
    JRASERVER-72126Create documentation on how to use Jira (Jira boards) using Screen Readers
  41. Suggestion
    JRASERVER-72440Issue Comments Experience Improvement
  42. Suggestion
    JRASERVER-72547Deleting plans in bulk mode for Advanced Roadmaps
  43. Suggestion
    JRASERVER-72671ability to add project and other readonly system fields to transition screen
  44. Suggestion
    JRASERVER-72760Moving an issue back to a previous project SHOULD re-use the 'old' issue key
  45. Suggestion
    JRASERVER-72885Save boards last viewed date
  46. Suggestion
    JRASERVER-73037Display Audit log in user profile language
  47. Suggestion
    JRASERVER-74503Display the 'Show all issues' link on the bottom of the Backlog
  48. Suggestion
    JRASERVER-74951Allow customization of attachment suffix
  49. Suggestion
    JRASERVER-75465Setting Default Tab Displayed on Screen by Issue Type
  50. Suggestion
    JRASERVER-76182As a Jira administrator I would like file replication from disaster recovery to work on manual actions made on the installed-plugins directory
Refresh results
<< Previous 13 14 15 16 17Next >>
701 of 7884
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-78795

Ongoing recurring SLA field

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Administration - Workflows
    • None
    • 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.

      Team

       

      in ITSM , we at times have recurring response SLAs for P1 /P2 critical cases.  These response SLA are for continuous updates  and not the same as IRT which is a one time SLA.

      The Ongoing response SLA begins after an Initial response is met - this is a quality SLA for ensuring like for P1 every hourly an update should go to customer until solution. This is critical for ITSM to track the ongoing response too.  Can a field of recurring SLA be added in Jira SM for managing the reponsiveness and this isnt just about a notification or template but a SLA for a support to manually enter updates /technical information for customer.

       

            • All
            • Comments
            • Work Log
            • History
            • Activity
            Vidhi Raman Chandra created issue - 08/May/2025 12:33 PM

              Unassigned Unassigned
              ff4d47596adf Vidhi Raman Chandra
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                08/May/2025 12:33 PM
                Updated:
                08/May/2025 12:33 PM
                • Atlassian Jira Project Management Software
                • About Jira
                • Report a problem
                • Privacy policy
                • Notice at Collection

                Atlassian