Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why is the behavior of bi-directional sync of date fields (released in 10.91) inconsistent?

In preparation for adopting the bi-directional sync of date fields, the following scenarios where tested. In each scenario, the date field always pushed to the other system, with the exception of scenario 2. Is that intentional? If so, why?

Scenario 1: Feature has dates / Jira Epic does not / Update Jira Epic

In this scenario the JA feature has date values, the Jira Epic does not. I applied a label to the Jira Epic issue. When information synced from Jira to Jira Align, the dates in the JA Feature issue were removed (set to blank).

Scenario 2: Jira Epic has dates / Feature does not / Update the Feature

In this scenario, the Jira Epic issue has date values, the Jira Align Feature does not. I updated the description in the Jira Align Feature. When information synced from Jira Align to Jira, the dates on the Jira Epic issue were not removed, i.e. they were retained.


Extending this to scenarios where both systems have dates...

Scenario 3: Feature and Jira Epic have dates / Jira Epic updated first after implementing this change request

Immediately after implementing this change request, if both the Feature AND the Jira Epic have different date values and the Jira Epic is updated first... The date values from the Jira Epic will be applied to the Jira Align Feature.

Scenario 4: Feature and Jira Epic have dates / Feature updated first after implementing this change request

Immediately after implementing this change request, if both the Feature AND the Jira Epic have different date values and the Feature is updated first... The date values from the Jira Align Feature will be applied to the Jira Epic issue.

 

 

1 answer

1 accepted

1 vote
Answer accepted
Mark Cruth Atlassian Team May 06, 2021

Hi @Diane Raber!

Great question! My thought here is that in scenario 2, Jira Align is intentionally keeping the dates to avoid wiping out dates for customers if they had been using dates in Jira prior and nothing is populated in Jira Align. I'm curious...if you had the same setup as scenario 2 (no dates in Jira Align, date in Jira) and updated the Jira description (vs the Jira Align description), do the dates sync over? 

I do think this is worth submitting a support ticket to request clarification / potentially call out a bug. Here's the support link: https://support.atlassian.com/contact/

Mark

Will do, thanks Mark!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Align

Helpful hints if you're rolling Align out to your entire enterprise

(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...

1,352 views 3 28
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you