Uploaded image for project: 'Minyaa Suite'
  1. Minyaa Suite
  2. MYAA-513

'TimeTracking' section on Issue Screen disappears after Minyaa Time installation. How to restore it?

    XMLWordPrintableJSON

    Details

    • Type: Support Request
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.5
    • Fix Version/s: 1.8
    • Component/s: Plugin Time Management
    • Security Level: Public
    • Labels:
      None
    • JIRA Release:
      4.0.0

      Attachments

        Issue Links

          Activity

          Hide
          vthoule Vincent Thoulé added a comment -

          Oksana,

          Normally, Minyaa has no effect on TimeTracking activation.
          Verify its activation on http://yourDomain/jira/secure/admin/jira/TimeTrackingAdmin!default.jspa

          I am searching for other root cause ...

          V.

          Show
          vthoule Vincent Thoulé added a comment - Oksana, Normally, Minyaa has no effect on TimeTracking activation. Verify its activation on http://yourDomain/jira/secure/admin/jira/TimeTrackingAdmin!default.jspa I am searching for other root cause ... V.
          Hide
          oksana Oksana Morozhenko added a comment -

          Time Tracking

          Time Tracking is currently ON.
          The number of working hours per day is 8.
          The number of working days per week is 5.
          Time estimates will be displayed in the following format: pretty (e.g. 4 days, 4 hours, 30 minutes)
          The current default unit for time tracking is minute.
          Note: To change these values deactivate and then reactivate Time Tracking.

          For the users you wish to be able to log work on issues, ensure that they have the Work On Issues permission in the relevant permission scheme.

          To deactivate Time Tracking, simply click below

          Show
          oksana Oksana Morozhenko added a comment - Time Tracking Time Tracking is currently ON. The number of working hours per day is 8. The number of working days per week is 5. Time estimates will be displayed in the following format: pretty (e.g. 4 days, 4 hours, 30 minutes) The current default unit for time tracking is minute. Note: To change these values deactivate and then reactivate Time Tracking. For the users you wish to be able to log work on issues, ensure that they have the Work On Issues permission in the relevant permission scheme. To deactivate Time Tracking, simply click below
          Hide
          oksana Oksana Morozhenko added a comment -

          I made following experiment:
          1. Install standalone JIRA 4.0.1 on a clear computer. Add a project and an issue.
          2. TimeTracking section on Issue screen was present.
          3. Add Minyaa Time plugin (only need jar files) and our commercial license.
          4. TimeTracking section disappeared.

          Show
          oksana Oksana Morozhenko added a comment - I made following experiment: 1. Install standalone JIRA 4.0.1 on a clear computer. Add a project and an issue. 2. TimeTracking section on Issue screen was present. 3. Add Minyaa Time plugin (only need jar files) and our commercial license. 4. TimeTracking section disappeared.
          Hide
          vthoule Vincent Thoulé added a comment -

          I find

          It is linked to the Time Tracking Security implementation :
          See http://www.minyaa.com/documentation/latest/Features/ModuleTime/TimeTrackingSecurity.html

          Defaulty Timetrarking section is show only if TimeTracking is activated.
          With Minyaa, you must to have the field in the Screen definition.

          Show
          vthoule Vincent Thoulé added a comment - I find It is linked to the Time Tracking Security implementation : See http://www.minyaa.com/documentation/latest/Features/ModuleTime/TimeTrackingSecurity.html Defaulty Timetrarking section is show only if TimeTracking is activated. With Minyaa, you must to have the field in the Screen definition.
          Hide
          oksana Oksana Morozhenko added a comment -

          I have Time Tracking field for ALL Screens.

          Show
          oksana Oksana Morozhenko added a comment - I have Time Tracking field for ALL Screens.
          Hide
          vthoule Vincent Thoulé added a comment -

          May you check that includes/panels/issue/view_timetracking.jsp has been modified with a backup includes/panels/issue/view_timetracking.jsp.myaa

          Changes applied are :

          <webwork:if test="applicationProperties/option('jira.option.timetracking') == true">
          

          replace by

           
          <webwork:if test="applicationProperties/option('jira.option.timetracking') == true && /timeTrackingVisible == true">
          

          I have just made a test with 4.0.0 without trouble. I make a new one with 4.0.1

          V.

          Show
          vthoule Vincent Thoulé added a comment - May you check that includes/panels/issue/view_timetracking.jsp has been modified with a backup includes/panels/issue/view_timetracking.jsp.myaa Changes applied are : <webwork:if test= "applicationProperties/option( 'jira.option.timetracking' ) == true" > replace by <webwork:if test= "applicationProperties/option( 'jira.option.timetracking' ) == true && /timeTrackingVisible == true" > I have just made a test with 4.0.0 without trouble. I make a new one with 4.0.1 V.
          Hide
          vthoule Vincent Thoulé added a comment -

          No Problem with 4.0.1

          Without Minyaa,
          TimeTracking section is shown in View Screen when :

          • TimeTracking is activated

          TimeTracking section is shown in Edit Screen when :

          • TimeTracking is activated
          • and TimeTrackingField is present in Edit Issue Screen

          With Minyaa,
          TimeTracking section is shown in View Screen when :

          • TimeTrackingField is present in View Issue Screen
          • and that TimeTracking is activated

          TimeTracking section is shown in Edit Screen when :

          • TimeTracking is activated
          • and TimeTrackingField is present in Edit Issue Screen

          I did not reproduced your problem
          Have you other details ?

          V.

          Show
          vthoule Vincent Thoulé added a comment - No Problem with 4.0.1 Without Minyaa, TimeTracking section is shown in View Screen when : TimeTracking is activated TimeTracking section is shown in Edit Screen when : TimeTracking is activated and TimeTrackingField is present in Edit Issue Screen With Minyaa, TimeTracking section is shown in View Screen when : TimeTrackingField is present in View Issue Screen and that TimeTracking is activated TimeTracking section is shown in Edit Screen when : TimeTracking is activated and TimeTrackingField is present in Edit Issue Screen I did not reproduced your problem Have you other details ? V.
          Hide
          oksana Oksana Morozhenko added a comment -

          I have replaced the string
          <webwork:if test="applicationProperties/option('jira.option.timetracking') == true && /timeTrackingVisible == true">
          with
          <webwork:if test="applicationProperties/option('jira.option.timetracking') == true">

          and TimeTracking became visible.

          Thank you!

          Show
          oksana Oksana Morozhenko added a comment - I have replaced the string <webwork:if test="applicationProperties/option('jira.option.timetracking') == true && /timeTrackingVisible == true"> with <webwork:if test="applicationProperties/option('jira.option.timetracking') == true"> and TimeTracking became visible. Thank you!
          Hide
          vthoule Vincent Thoulé added a comment -

          Hi Oksana,

          It resolves perhaps your issue, but I need to identify the root cause.
          Do you have any other usefull details.

          Regards
          Vincent

          Show
          vthoule Vincent Thoulé added a comment - Hi Oksana, It resolves perhaps your issue, but I need to identify the root cause. Do you have any other usefull details. Regards Vincent
          Hide
          oksana Oksana Morozhenko added a comment -

          Hi Vincent,

          I got the problem after:
          1. Installed JIRA 4.0.1 Standalone on MSSQL.
          2. Installed Minyaa Time (only need jar files).

          Did you try to do it and see TimeTracking section?
          If yes, I'll recreate that on my environment again.

          Oksana.

          Show
          oksana Oksana Morozhenko added a comment - Hi Vincent, I got the problem after: 1. Installed JIRA 4.0.1 Standalone on MSSQL. 2. Installed Minyaa Time (only need jar files). Did you try to do it and see TimeTracking section? If yes, I'll recreate that on my environment again. Oksana.
          Hide
          vthoule Vincent Thoulé added a comment -

          Thks

          Yes, I made the test and do not success to reproduce the issue.
          I will make a new test with Time plugins only.

          Bob (MYAA-511) encountered the same trouble with the Full edition!

          Show
          vthoule Vincent Thoulé added a comment - Thks Yes, I made the test and do not success to reproduce the issue. I will make a new test with Time plugins only. Bob ( MYAA-511 ) encountered the same trouble with the Full edition!
          Hide
          bob.swift Bob Swift added a comment -

          Oksana's changed worked for me too! And the following also worked:

          && /timeTrackingVisible != false
          

          I also have time tracking field on all relevant displays.

          Show
          bob.swift Bob Swift added a comment - Oksana's changed worked for me too! And the following also worked: && /timeTrackingVisible != false I also have time tracking field on all relevant displays.
          Hide
          vthoule Vincent Thoulé added a comment -

          Hi Oksana, Bob,

          The applied solution let me know what could be the root cause ...

          My latest test :
          I made some changes in view_timetracking.jsp, and do not reproduce your issue.
          The both changes timeTrackingVisible != false and timeTrackingVisible == true are valids.

          It appears that your issue seems to be linked to Tomcat (re)compilation.
          I am not sure which exact scenario you encountered

          Context :

          • viewissue.jsp
          • view_timetracking.jsp is included in viewissue.jsp

          Minyaa Installation starts

          • viewissue.jsp modified by Minyaa Core
          • view_timetracking.jsp modified by Minyaa Time
          • J2EE Server may have started to recompile viewissue.jsp and its include before than view_timetracking.jsp is modified, and does not perform another recompilationm when view_timetracking.jsp is modified.

          I will try to implement a fix in next release, but as I did not successed to reproduce the error (the context should depends on Tomcat release, JVM release and/or Host machine capacities), I won't be able to confirm the correction.

          Then you can rollback to minyaa's modification. It should work fine.

          Regards
          Vincent

          Show
          vthoule Vincent Thoulé added a comment - Hi Oksana, Bob, The applied solution let me know what could be the root cause ... My latest test : I made some changes in view_timetracking.jsp, and do not reproduce your issue. The both changes timeTrackingVisible != false and timeTrackingVisible == true are valids. It appears that your issue seems to be linked to Tomcat (re)compilation. I am not sure which exact scenario you encountered Context : viewissue.jsp view_timetracking.jsp is included in viewissue.jsp Minyaa Installation starts viewissue.jsp modified by Minyaa Core view_timetracking.jsp modified by Minyaa Time J2EE Server may have started to recompile viewissue.jsp and its include before than view_timetracking.jsp is modified, and does not perform another recompilationm when view_timetracking.jsp is modified. I will try to implement a fix in next release, but as I did not successed to reproduce the error (the context should depends on Tomcat release, JVM release and/or Host machine capacities), I won't be able to confirm the correction. Then you can rollback to minyaa's modification. It should work fine. Regards Vincent
          Hide
          bob.swift Bob Swift added a comment -

          The problem occurs even after numerous jira server restarts, so it is hard to imagine this being a tomcat issue. With timeTrackingVisible != false working implies that timeTrackingVisible is null and would point to some sort of initialization problem.

          Show
          bob.swift Bob Swift added a comment - The problem occurs even after numerous jira server restarts, so it is hard to imagine this being a tomcat issue. With timeTrackingVisible != false working implies that timeTrackingVisible is null and would point to some sort of initialization problem.
          Hide
          vthoule Vincent Thoulé added a comment -

          Even if the JIRA Server restart, if the timestamp of compiled viewissue.jsp is newer that timestamp of the view_timetracking.jsp, viewissue.jsp will not be recompiled.

          Code of isTimeTrackingVisible is as follow :

          public boolean isTimeTrackingVisible() {
           FieldScreenRenderer editFieldScreenRenderer = fieldScreenRendererFactory.getFieldScreenRenderer(getRemoteUser(), getIssueObject(), IssueOperations.EDIT_ISSUE_OPERATION, false);
           return editFieldScreenRenderer.getFieldScreenRenderLayoutItem(fieldManager.getOrderableField(IssueFieldConstants.TIMETRACKING)).isShow(getIssueObject());
          }
          

          In my tests, I do not success to encounter a Null !
          I will keep the TrackingVisible != false in next releases

          Regards
          Vincent

          Show
          vthoule Vincent Thoulé added a comment - Even if the JIRA Server restart, if the timestamp of compiled viewissue.jsp is newer that timestamp of the view_timetracking.jsp, viewissue.jsp will not be recompiled. Code of isTimeTrackingVisible is as follow : public boolean isTimeTrackingVisible() { FieldScreenRenderer editFieldScreenRenderer = fieldScreenRendererFactory.getFieldScreenRenderer(getRemoteUser(), getIssueObject(), IssueOperations.EDIT_ISSUE_OPERATION, false ); return editFieldScreenRenderer.getFieldScreenRenderLayoutItem(fieldManager.getOrderableField(IssueFieldConstants.TIMETRACKING)).isShow(getIssueObject()); } In my tests, I do not success to encounter a Null ! I will keep the TrackingVisible != false in next releases Regards Vincent

            People

            Assignee:
            vthoule Vincent Thoulé
            Reporter:
            oksana Oksana Morozhenko
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 0.75h
                0.75h