Structure Plugin representation of Dates off by a day

[Aaron Gage]

Not sure if this question is in the right place, but tired of searching for an answer.... :)

Using Structure plugin for Data Center version v7.3.

Trying to write automation to assess when our Target End dates are out of alignment with our Fix Version, but within the structure, it always seems to represent the Target End Date as 1 day off of what's actually stored in the issue...  i.e. when I enter 11/1/2022, structure represents this data as 10/31/2022 and thus "fails" the automation check to ensure the Target End data aligns with the end of the Program Increment.

If I double click the field again, 11/1/2022 shows up, but upon closing the edit field dialogue, 10/31/2022 is displayed!  If I open the Issue in JIRA only, it correctly displays 11/1/2022....

Is there some sort of timezone thing going on?  Is there a work around for this phenomenon?

Pictures of issue attached.

[Dave Rosenlund _Trundl_ · Accepted solution]

Hi, @Aaron Gage.

First/best guess: This can happen when the underlying Jira system is in a significantly different time zone — or Jira's date/time is misconfigured.  I.e., Structure gets date and time info. from Jira. 

If that's not the situation in your case please reach out to the Tempo / ALM Works support team and they'll help you diagnose:  support@almworks.com

Hope this helps,

-dave 

[Chris O]

I am having this same issue.

I have verified that my JIRA system is in the correct timezone and displaying the correct time. (JIRA -> Administration -> System Info ... -0500 for me)

Does anyone know how I can find what timezone Structure thinks it is in?

I've looked through documentation and all the settings in the  Structure Administration settings. (Also, running Structure 8.2.1 on JIRA 9.2 Data Center)

[David Niro]

Hi @Chris O ,

Structure is going to use date and time info from Jira. 

We will probably need to ask you for information that is better shared directly with the support team.  Could you please reach out via support@almworks.com or through our customer portal support.almworks.com?  We will be happy to review with you in more detail.

Best,
David

[petemo94]

@Aaron Gage did you ever find the reason for this problem? I'm still seeing it as well. Been that way for years. 

[Dave Rosenlund _Trundl_]

Hi, @petemo94.  Give the Structure support team a try. I bet they can help you discover the source of the problem. 

[Aaron Gage]

@petemo94 Nope.....just making due with date ranges for checking and assuming anything that doesn't meet the date range is in the noise.

[Stepan Kholodov _Tempo_]

Hello @Aaron Gage @petemo94 @Chris O 

In Structure version 8.3 a fix was delivered for a problem with Target start/Target end fields that caused their values to be displayed incorrectly. Please upgrade Structure to this version or to the latest version and see if it helps.

If it doesn't, please reach out to us directly at our support portal and we'll investigate this matter.

Best regards,
Stepan Kholodov
Tempo

[Aaron Gage]

Sounds great Stepan.  Now to wait for my organization to finish the 95 approvals necessary to update any software suite/plug-in.... :D