Summary

      Commenting on a snippet review fails with the following error presented in the web interface:

      Steps to Reproduce

      1. Create a snippet review having any content
      2. Click on source lines to add a comment
      3. Type anything in the comment box and click "Post"

      Expected Results

      The comment should be posted.

      Actual Results

      The comment is not posted and the below exception is thrown in the atlassian-fisheye.log file:

      2018-11-27 16:43:03,697 DEBUG [qtp2017797638-211 ] fisheye ProfilingServletFilter-logRequest - start request POST /gwt/SnippetRPCService sessionid=on0io8ei3xdk1u8m8fwbwgz3n
      2018-11-27 16:43:03,701 DEBUG [qtp2017797638-211 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fkraemer' in directory 1 'Internal Directory'
      2018-11-27 16:43:03,704 DEBUG [qtp2017797638-211 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fkraemer' in directory 1 'Internal Directory'
      2018-11-27 16:43:03,708 DEBUG [qtp2017797638-211 ] fisheye TxHelperStylePlatformTransactionManager-rollback - Rolled back transaction started from:
      java.lang.Throwable: (Stack trace at transaction depth 0 start)
      	at com.cenqua.crucible.hibernate.SessionState.pushTxBeginStacktrace(SessionState.java:71) [fisheye.jar:?]
      	at com.cenqua.crucible.hibernate.SessionState.beginTx(SessionState.java:61) [fisheye.jar:?]
      	at com.cenqua.crucible.hibernate.HibernateUtil.beginTransaction(HibernateUtil.java:372) [fisheye.jar:?]
      	at com.atlassian.fecru.tx.TxHelperStylePlatformTransactionManager.getTransaction(TxHelperStylePlatformTransactionManager.java:34) [fisheye.jar:?]
      	at com.cenqua.crucible.hibernate.TxHelper.beginTx(TxHelper.java:19) [fisheye.jar:?]
      	at com.atlassian.fecru.gwt.snippet.server.SnippetRPCServiceImpl.beginTx(SnippetRPCServiceImpl.java:92) [fisheye.jar:?]
      	at com.atlassian.fecru.gwt.snippet.server.SnippetRPCServiceImpl.createInlineComment(SnippetRPCServiceImpl.java:160) [fisheye.jar:?]
      	...
      2018-11-27 16:43:03,711 DEBUG [qtp2017797638-211 ] fisheye ProfilingServletFilter-logRequest - end request in 14ms POST /gwt/SnippetRPCService sessionid=on0io8ei3xdk1u8m8fwbwgz3n 200 mem=1.390MB
      

      Notes

      Probably related to the bug reported at CRUC-7410, because the error reported at CRUC-7410 happens after clicking on source lines to add a comment (which is the second step for replicating this bug here)

      Workaround

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

            [CRUC-8360] Error commenting on snippet review

            If you are not planning to fix it. How about removing the option in the GUI?

            It gives a bad feeling in using Crucible, if this option is offered next to creating a review (drop down box next to create review) and then - by intention - fails.

            Michael Möllney added a comment - If you are not planning to fix it. How about removing the option in the GUI? It gives a bad feeling in using Crucible, if this option is offered next to creating a review (drop down box next to create review) and then - by intention - fails.

            Atlassian Update – 10 January 2022

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it.

            We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details.

            If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 10 January 2022 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it. We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details. If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates. Kind regards Marek Parfianowicz Development Team Lead

              Unassigned Unassigned
              fkraemer Felipe Kraemer
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: