Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-21621

Jira Calendar Dashboard Gadget isn't respecting selected value

    • 9.03
    • 20
    • Severity 3 - Minor
    • 183
    • Hide
      Atlassian Update – 29 May 2023

      Dear Customers,
      We're happy to announce that this issue is fixed in 6.0.2 and 6.1.2 releases.

      Best regards
      Grzegorz Kulinski
      Jira DC developer

      Show
      Atlassian Update – 29 May 2023 Dear Customers, We're happy to announce that this issue is fixed in 6.0.2 and 6.1.2 releases. Best regards Grzegorz Kulinski Jira DC developer

      Problem

      Customer is seeing issues with the Jira Calendar Plugin after updating it to 6.0.1. When selecting any value (except for Target End and Target Start) for the Date to Display attribute in the Jira Calendar Gadget, the returning result assumes that Created is the value selected, which is not correct.

      Environment

      Jira Data Center 9.3.1
      Jira Software Server 9.3.1

      Steps to Reproduce

      1. Install Jira Software Server 9.3.1.
      2. Install Jira Calendar Plugin 6.0.1
      3. Create a new Dashboard
      4. Add the Jira Calendar Gadget
      5. Set the "Date to Display" value to the following:
        1. Created
        2. Due Date
        3. Last Viewed
        4. Resolved
        5. Updated
      6. Calendar should show "Created" as the value which is not expected.

      Expected Results

      We expect that the "Date to Display" set value should be the result returned.

      Actual Results

      We see that the value selected for "Date to Display" always set as "Created"

      Workaround

      Downgrade to Jira Calendar Plugin 6.0.0 by downloading/uploading the JAR file from the Marketplace version history.

      1. While logged in as a Jira administrator, navigate to ⚙️ (gear icon) > Manage apps > Manage apps.
      2. Select JIRA Calendar Plugin and then uninstall.
      3. Open the upload app modal and enter https://marketplace.atlassian.com/download/apps/293/version/400000320 in the from this URL field.
      4. Click upload.

      Notes

            [JSWSERVER-21621] Jira Calendar Dashboard Gadget isn't respecting selected value

            Hello!

            I just updated to the newest version and now it works also with 6.1.2.

            Thank you, Roland

            Roland Paulus added a comment - Hello! I just updated to the newest version and now it works also with 6.1.2. Thank you, Roland

            Hi d8cbcac22823, some time has passed but there is fixed version of the calendar for your problem. Please, let me know if this solves your issue.

            Maciej Szarecki added a comment - Hi d8cbcac22823 , some time has passed but there is fixed version of the calendar for your problem. Please, let me know if this solves your issue.

            hello!

            i just created a new date/time field in our testing system an associated it with a field configration scheme.

            • Good news: it works fine, i can select it via the plugin and it shows the right date in the widget
            • Bad news: That doesn't help me with our existing fields as they are widely used in a lot of Jira Issues and i can't create a new field wich replaces the existing one. and ist still works wih plugin version 6.0.2 

            Roland Paulus added a comment - hello! i just created a new date/time field in our testing system an associated it with a field configration scheme. Good news: it works fine, i can select it via the plugin and it shows the right date in the widget Bad news: That doesn't help me with our existing fields as they are widely used in a lot of Jira Issues and i can't create a new field wich replaces the existing one. and ist still works wih plugin version 6.0.2 

            d8cbcac22823, I'm really confused right now so I'd like to ask 2 more questions:

            1. Have You tried to do this using sys admin account or any other with all privileges?
            2. Try to create new global date custom field without any association and try to select it in calendar gadget. Does the problem still exist?

            Thanks in advance for Your answers.

            Maciej Szarecki added a comment - d8cbcac22823 , I'm really confused right now so I'd like to ask 2 more questions: Have You tried to do this using sys admin account or any other with all privileges? Try to create new global date custom field without any association and try to select it in calendar gadget. Does the problem still exist? Thanks in advance for Your answers.

            hi!

            thank you, but i'm sorry to tell you, that, after updating the version to 6.1.1 in our testing system, the problem still persists.

             

            • when i try to change the widget date to display to our custom field,
            • it switches back to "due date"

            Roland Paulus added a comment - hi! thank you, but i'm sorry to tell you, that, after updating the version to 6.1.1 in our testing system, the problem still persists.   when i try to change the widget date to display to our custom field, it switches back to "due date"

            d8cbcac22823, 6.1.1 is released You can try it.

            Maciej Szarecki added a comment - d8cbcac22823 , 6.1.1 is released You can try it.

            to be honest i don't understand your last question. what do you mean with user has or has no acces to any project. maybe you can add a screenshot.

             

            as of now, every user has access to edit the custom date field, when he creates or edits a Jira Issue with the specifix issue type. and there are no differences.

             

            the only difference is:

            • using plugin version 6.0.2 with Jira version 9.8.1: calender widget works fine
            • using plugin version 6.1.0 with Jira version 9.8.1: calender widget works fine - computer says no

            Roland Paulus added a comment - to be honest i don't understand your last question. what do you mean with user has or has no acces to any project. maybe you can add a screenshot.   as of now, every user has access to edit the custom date field, when he creates or edits a Jira Issue with the specifix issue type. and there are no differences.   the only difference is: using plugin version 6.0.2 with Jira version 9.8.1: calender widget works fine using plugin version 6.1.0 with Jira version 9.8.1: calender widget works fine - computer says no

            d8cbcac22823, so context is global. Last question: on the instance, is there any existing project to which user has access? or user has no access to any project / there's no project on the instance?

            Maciej Szarecki added a comment - d8cbcac22823 , so context is global. Last question: on the instance, is there any existing project to which user has access? or user has no access to any project / there's no project on the instance?

            hi! 

             

            to 1: 

            • it is not project specific but specific to a custom issue type, whicht belongs to a screen them, that nearly every project is assigned to

             

            to 2 and 3:

            • everybody who uses this specific issue type can edit these custom fields
            • the context is global (for all projects)

             

            as i mentioned before, is everything working fine, when we use the plugin version 6.0.2 as mentioned in the fix-version of this Jira issue. The problem occurs only again, when we update to the latest version 6.1.0.

            Roland Paulus added a comment - hi!    to 1:  it is not project specific but specific to a custom issue type, whicht belongs to a screen them, that nearly every project is assigned to   to 2 and 3: everybody who uses this specific issue type can edit these custom fields the context is global (for all projects)   as i mentioned before, is everything working fine, when we use the plugin version 6.0.2 as mentioned in the fix-version of this Jira issue. The problem occurs only again, when we update to the latest version 6.1.0.

            Maciej Szarecki added a comment - - edited

            d8cbcac22823, thanks again for Your answers I have 3 more questions:

            1. Is this custom field set as global or available only for selected projects?
            2. if this custom field is set as global - does user have access to any existing project?
            3. If this custom field is set as available only for selected projects - does user have access to any associated project?

            Maciej Szarecki added a comment - - edited d8cbcac22823 , thanks again for Your answers I have 3 more questions: Is this custom field set as global or available only for selected projects? if this custom field is set as global - does user have access to any existing project? If this custom field is set as available only for selected projects - does user have access to any associated project?

            Hi!

            To 1:

            We came from Jira 9.6 and updated to 9.8.1

            To 2

            • As we experienced the Calendar Problem with Version 6.0.1 while using Jira 9.6 we experienced the known problem an did the workaround in downgrading to 6.0.0.
            • We deleted the Plugin an installed a fresh 6.0.0 Version
            • In our Testsystem with Jira 9.8.1 we updated the plugin after the release to 6.1.0 with the autmatic updates.
            • So we tried our luck with downgrading to 6.0.2. We did the same procedure as above, deleting calendar version 6.1.0 and installing version 6.0.2
            • Yesterday we upgraded our producitve system to Jira 9.8.1 and as of now use the 6.0.2 release of the plugin

            To 3

            • Correct, we see all the system and custom date fields

            To 4

            • when i select a custom field, it changes to i think "due date" (we use it in german, where this field is named "Fälligkeitsdatum")
            • Other system fieds for example created or updated work fine

             

            I just updated the plugin to 6.1.0 while running on Jira 9.8.1, in our Test System the problem persists.

            I hope that my answers help you, discover the problem.

            Best regards,

            Roland

            Roland Paulus added a comment - Hi! To 1: We came from Jira 9.6 and updated to 9.8.1 To 2 As we experienced the Calendar Problem with Version 6.0.1 while using Jira 9.6 we experienced the known problem an did the workaround in downgrading to 6.0.0. We deleted the Plugin an installed a fresh 6.0.0 Version In our Testsystem with Jira 9.8.1 we updated the plugin after the release to 6.1.0 with the autmatic updates. So we tried our luck with downgrading to 6.0.2. We did the same procedure as above, deleting calendar version 6.1.0 and installing version 6.0.2 Yesterday we upgraded our producitve system to Jira 9.8.1 and as of now use the 6.0.2 release of the plugin To 3 Correct, we see all the system and custom date fields To 4 when i select a custom field, it changes to i think "due date" (we use it in german, where this field is named "Fälligkeitsdatum") Other system fieds for example created or updated work fine   I just updated the plugin to 6.1.0 while running on Jira 9.8.1, in our Test System the problem persists. I hope that my answers help you, discover the problem. Best regards, Roland

            Maciej Szarecki added a comment - - edited

            Hi d8cbcac22823, I'd like to ask a few questions:

            1. Did You updated from Jira version lower than 9.7.0?
            2. Have You tried to delete and create calendar again?
            3. I assume that when You edit the calendar You see mentioned custom field in the dropdown but when you select it then calendar shows other field, right?
            4. Which field is shown instead of the selected?

            Thanks in advance for Your answers.

            Maciej Szarecki added a comment - - edited Hi d8cbcac22823 , I'd like to ask a few questions: Did You updated from Jira version lower than 9.7.0? Have You tried to delete and create calendar again? I assume that when You edit the calendar You see mentioned custom field in the dropdown but when you select it then calendar shows other field, right? Which field is shown instead of the selected? Thanks in advance for Your answers.

            hi!

            we have recently updated to Jira Software 9.8.1 and its a custom field.

            Roland Paulus added a comment - hi! we have recently updated to Jira Software 9.8.1 and its a custom field.

            Hi d8cbcac22823,
            Thank you for taking the time to comment on this issue. Which version of Jira are you using? Does this issue occur with system or custom field?

            Grzegorz Kuliński (Inactive) added a comment - - edited Hi d8cbcac22823 , Thank you for taking the time to comment on this issue. Which version of Jira are you using? Does this issue occur with system or custom field?

            Hello!

            We just tried to install Version 6.1.0 and the problem still exists, when we downgrades to die Fixversion 6.0.2 it worked.

            Can it be, that, what you wrote in Current Status is wrong?

            Roland Paulus added a comment - Hello! We just tried to install Version 6.1.0 and the problem still exists, when we downgrades to die Fixversion 6.0.2 it worked. Can it be, that, what you wrote in Current Status is wrong?

            Atlassian Update – 29 May 2023

            Dear Customers,
            We're happy to announce that this issue is fixed in 6.0.2 and 6.1.0 releases.

            Best regards
            Grzegorz Kulinski
            Jira DC developer

            Grzegorz Kuliński (Inactive) added a comment - - edited Atlassian Update – 29 May 2023 Dear Customers, We're happy to announce that this issue is fixed in 6.0.2 and 6.1.0 releases. Best regards Grzegorz Kulinski Jira DC developer

            When can we expect a real fix for this?

            Downgrading to the older version when the newer version has security fixes is not really reassuring.

            Francisco Villar Romasanta added a comment - When can we expect a real fix for this? Downgrading to the older version when the newer version has security fixes is not really reassuring.

            Thanx for that hint Damian. I also downgraded to 6.0.0 and the Bug is fixed for me. 

            BTW Atlassian, its a shame that you are investigating since Feb 9 for such an obvious bug ! 

            Andreas Heidrich added a comment - Thanx for that hint Damian. I also downgraded to 6.0.0 and the Bug is fixed for me.  BTW Atlassian, its a shame that you are investigating since Feb 9 for such an obvious bug ! 

            Damian Egli added a comment - - edited

            Using Calendar 6.0.0 did the trick for me! thanks to Atlassian Support

            Damian Egli added a comment - - edited Using Calendar 6.0.0 did the trick for me! thanks to Atlassian Support

            I think the version number of the plugin may be wrong here. It affects version 6.0.1 of the Jira Calendar Plugin, not 9.3.1. Also, for what it's worth, is there a way to report this as a bug with that plugin, rather than all of Jira?

            Dov Frankel added a comment - I think the version number of the plugin may be wrong here. It affects version 6.0.1 of the Jira Calendar Plugin, not 9.3.1. Also, for what it's worth, is there a way to report this as a bug with that plugin, rather than all of Jira?

              b5681d69ff53 Maciej Szarecki
              1cbcaa6c90d8 Adrian Castillo
              Affected customers:
              15 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: