Issue Summary

      Users are still able to log hours through the MS Teams, even after we disabled this functionality on JIRA following this KB:
      https://confluence.atlassian.com/jirakb/how-to-disable-the-log-work-option-in-jira-715129243.html

      Steps to Reproduce

      1. Follow all the steps of this KB to disable the Log work hours: https://confluence.atlassian.com/jirakb/how-to-disable-the-log-work-option-in-jira-715129243.html
      2. In the MS Teams app, in the chatBot, write the ticket number and sent it.
      3. The bot will send you a preview of the ticket with the "Log Work" button.
      4. Click there, select Custom, and insert a big number.
      5. The hours will be logged in the ticket.

      Sample:

      Expected Results

      MS Teams won't let users log hours if the modules are disabled based on the KB:
      https://confluence.atlassian.com/jirakb/how-to-disable-the-log-work-option-in-jira-715129243.html

      Actual Results

      The users are able to log hours through the MS Teams

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            [JSWSERVER-21876] Log Work still available on MS even if we disable on JIRA

            Aakrity Tibrewal (Inactive) made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Aakrity Tibrewal (Inactive) made changes -
            Labels New: cleanup-seos-fy25

            Atlassian Update - 14 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal (Inactive) added a comment - Atlassian Update - 14 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Data Center
            Marek Parfianowicz made changes -
            Occurrence Factor New: 10% [ 12830 ]
            Marek Parfianowicz made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Marek Parfianowicz made changes -
            Affects Version/s Original: 9.10.1 [ 105527 ]
            Affects Version/s New: JSMT 2022.08.101 [ 105741 ]
            Marek Parfianowicz made changes -
            Introduced in Version Original: 9.1
            Bugfix Automation Bot made changes -
            Introduced in Version New: 9.1
            Marek Parfianowicz made changes -
            Component/s Original: Jira Server for Teams [ 61899 ]
            Component/s New: Microsoft Teams for Jira Integration [ 62096 ]
            Key Original: API-301 New: JSWSERVER-21876
            Symptom Severity Original: Severity 2 - Major [ 14431 ] New: Severity 3 - Minor [ 15832 ]
            Affects Version/s Original: None [ 92938 ]
            Affects Version/s New: 9.10.1 [ 105527 ]
            Project Original: Atlassian Product Integrations [ 20010 ] New: Jira Software Server and Data Center [ 12200 ]
            Mauricio Cardoso (Inactive) made changes -
            Comment [ A comment with security level 'atlassian-staff' was removed. ]

              Unassigned Unassigned
              e4a30e15fd9f Mauricio Cardoso (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: