BIG PICTURE END DATE OVERWRITTEN. DUE DATE

[Mateusz Janus]

Hey,

when i edit Due Date BigPicture automatically overwrite the value and bring back legacy date. I have already seen other topics with this but did not find a solution. My config is like below

[Paweł Mazur · Accepted solution]

Hi Mateusz,

I'm Paweł from the Appfire Customer Success team, where we work on BigPicture. Thanks for reaching out!

It looks like we’ll need a bit more information to understand exactly what’s going on here. Since this involves a Data Center environment and some unexpected behavior, checking the Jira logs could give us more insight.

Could you please reach out through our support portal at this link? It would be super helpful if you could include the version of BigPicture you're using (if not the latest, can you confirm if the issue is on version 8.50.1). From there, we’ll take a closer look, and if needed, we’ll be happy to set up a call to dig deeper together.

Looking forward to getting this sorted out with you!

Cheers,
Paweł Mazur | Appfire

[Mateusz Janus]

Hello,

i run re-index process. Nothing happen BUT i can replicate the issue. The problem was only with legacy issues when Due Date was already provided. I opened new project from scratch and Due Date works fine without any Edit Issue. What i noticed between my NEW project and LEGAY one was this (below screen)

OLD project has such Risks configuration. My NEW project has no Due Date card under Risks.

I added this card to my project (same as above) and commit the change. 

Then i tried to edit Due Date on my project and after 1 sec Due Date value is BACK to original value

Issue: i removed this Due Date Card from Risks card. Run Re-index.

Results: Ticket with uneditable Due Date cannot still be edited. Entire time there is original value od Due Date. But when i open another ticket and edit Due Date there is no any issue.

It looks like tickets which were fullfiled with Due Date value in the moment when Due Date Card is there (under Risks) they are no longer able to be edited.

@Grzgoorz D. [BigPicture] @Lukasz Panek {BigPicture} @Anna-BigPicture can u support me with this>

[Mateusz Janus]

should i execute re-indexing process in such case? I have never done such things before. Is it risky or just need to click "start" and let it go? Are there any negative consequences after like tickets crash or linking?