Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-10668

Using fields Target Start and Target End displays one day off in Confluence calendar

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium
    • None
    • 8.20.2, 9.9.0
    • Integration, Reporting
    • None
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 21 August 2023

      Hi there,

      Thank you for reporting this issue. This appears to be a duplicate of a previously reported issue under the ticket JRASERVER-73401. In the interest of keeping our issue tracker tidy, and to track votes and watches in a single place, I'll be closing this ticket.

      Please refer to JRASERVER-73401 for updates on this issue.

      Best Regards,
      Daniel Rauf
      Software Engineer, Jira DC

      Show
      Atlassian Update – 21 August 2023 Hi there, Thank you for reporting this issue. This appears to be a duplicate of a previously reported issue under the ticket JRASERVER-73401 . In the interest of keeping our issue tracker tidy, and to track votes and watches in a single place, I'll be closing this ticket. Please refer to JRASERVER-73401 for updates on this issue. Best Regards, Daniel Rauf Software Engineer, Jira DC

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Use the Target Start and Target End dates in a Plan to set these two date/time points on an issue.  
      2. In Confluence team calendar, click Add Event
        1. Event Type: Jira Issue Dates
        2. Display: JQL (enter JQL to select an issue with a Target Start and Target End date that is set)
        3. Date Range: Start - Target start / End - Target end

      Expected Results

      The Issue shows up on the calendar with the correct dates

      Actual Results

      The issue shows up on the calendar with each value at one day prior.  Example = Issue shows up on calendar from Aug 12-16 but Jira issue shows Aug 13-17.

      The root cause seems to be that the field TYPE is not a date picker field but a special Advanced Roadmaps eponymous field.  

      Workaround

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

      Workaround not involving this field: Use a script, automation, or app to copy the Target Start and Target End fields into a date picker field then use the date picker field in the calendar. 

            [JPOSERVER-10668] Using fields Target Start and Target End displays one day off in Confluence calendar

            Sarah A added a comment -

            drauf - the workaround for the other Bug did not work for my customer, which is why we opened a new Bug.  

            Can we either reopen this one or remove the workaround on the other Bug report and add the root cause to it?  

            Sarah A added a comment - drauf - the workaround for the other Bug did not work for my customer, which is why we opened a new Bug.   Can we either reopen this one or remove the workaround on the other Bug report and add the root cause to it?  

            Daniel Rauf added a comment -
            Atlassian Update – 21 August 2023

            Hi there,

            Thank you for reporting this issue. This appears to be a duplicate of a previously reported issue under the ticket JRASERVER-73401. In the interest of keeping our issue tracker tidy, and to track votes and watches in a single place, I'll be closing this ticket.

            Please refer to JRASERVER-73401 for updates on this issue.

            Best Regards,
            Daniel Rauf
            Software Engineer, Jira DC

            Daniel Rauf added a comment - Atlassian Update – 21 August 2023 Hi there, Thank you for reporting this issue. This appears to be a duplicate of a previously reported issue under the ticket JRASERVER-73401 . In the interest of keeping our issue tracker tidy, and to track votes and watches in a single place, I'll be closing this ticket. Please refer to JRASERVER-73401 for updates on this issue. Best Regards, Daniel Rauf Software Engineer, Jira DC

              Unassigned Unassigned
              samann Sarah A
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: