-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
9.3.1, 9.4.1, 9.4.3
-
9.03
-
20
-
Severity 3 - Minor
-
183
-
-
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
- Install Jira Software Server 9.3.1.
- Install Jira Calendar Plugin 6.0.1
- Create a new Dashboard
- Add the Jira Calendar Gadget
- Set the "Date to Display" value to the following:
- Created
- Due Date
- Last Viewed
- Resolved
- Updated
- 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.
- While logged in as a Jira administrator, navigate to ⚙️ (gear icon) > Manage apps > Manage apps.
- Select JIRA Calendar Plugin and then uninstall.
- Open the upload app modal and enter https://marketplace.atlassian.com/download/apps/293/version/400000320 in the from this URL field.
- Click upload.
Notes
- is duplicated by
-
-
- Closed
-
- mentioned in
-
Page Failed to load
- relates to
-
RAID-3320 You do not have permission to view this issue
[JSWSERVER-21621] Jira Calendar Dashboard Gadget isn't respecting selected value
| Current Status |
Original:
{panel:title=Atlassian Update – 29 May 2023|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
Dear Customers, We're happy to announce that this issue is fixed in 6.0.2 and 6.1.1 releases. Best regards Grzegorz Kulinski Jira DC developer {panel} |
New:
{panel:title=Atlassian Update – 29 May 2023|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
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 {panel} |
| Comment | [ [~d8cbcac22823], right now I'm really confused as there should not be any problem, maybe there is a problem with some configurations on Your instance? May I get a backup zip for further investigation if there isn't any vulnerable data? ] |
| Current Status |
Original:
{panel:title=Atlassian Update – 29 May 2023|borderStyle=solid|borderColor=#deebff | titleBGColor=#deebff | bgColor=#deebff}
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 {panel} |
New:
{panel:title=Atlassian Update – 29 May 2023|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
Dear Customers, We're happy to announce that this issue is fixed in 6.0.2 and 6.1.1 releases. Best regards Grzegorz Kulinski Jira DC developer {panel} |
| Remote Link | Original: This issue links to "RAID-3320 (Bulldog)" [ 730239 ] | New: This issue links to "RAID-3320 (JIRA Server (Bulldog))" [ 730239 ] |
| Current Status |
New:
{panel:title=Atlassian Update – 29 May 2023|borderStyle=solid|borderColor=#deebff | titleBGColor=#deebff | bgColor=#deebff}
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 {panel} |
| Labels | New: raid |
| UIS | Original: 176 | New: 183 |
| Fix Version/s | New: 6.0.2 [ 27806 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |