Issues in project with the same configuration behave differently when created

[Paola Andrea Elli]

When I create issue in projects with the same exact configuration (+created with shared configuration)  they then behave differently. 

For one project when created it does not update the End and Start date.

While in other projects it updates automatically the End and Start date to the day prior to the login. (eg: I create the issue on July 20th it sets the End and Start date on 19th July) 

See the screenshot attached and the activity list as well for reference. 

ACTIVITY LIST 

[Kseniia Trushnikova · Accepted solution]

Hi @Paola Andrea Elli,

Fields can be set by automation rules or by other apps configurations (for example, Big Picture, have a look at this question: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Start-amp-End-date-in-BigPicture/qaq-p/1718379).

Can you check if these fields are set in Safe Mode?

[Paola Andrea Elli]

Hi @Kseniia Trushnikova  Thanks a lot! I believe we are on the right track with the suggestione about BigPicture https://jira.bigpicture.one/browse/ONE-6654. 

But: 

- when I create the issue it sets the data of the day before, why? Is it maybe for the time format of the app? 

- from where does it get the user to be shown in the jira history? Especially when the issue was an old one created in jira (without valorized dates) months before and included in Big picture just recently? 

[Kseniia Trushnikova]

@Paola Andrea Elli,

1. I can only guess that it's due to time zones... I've found this bug: https://jira.bigpicture.one/browse/ONE-53290
2. When I had a similar problem on our Jira instance, these fields were set on behalf of the leader of the program that contained such issues. Perhaps you have the same case.

Anyway, I would recommend you to contact Big Picture support: https://appfire.atlassian.net/servicedesk/customer/portal/42 I believe they can help.

[Paola Andrea Elli]

Thanks a lot!