Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Can't use custom date fields in for scheduling

Edited

We have added custom start and end dates to our Jira project and kanban board and are able to add the fields to AR dashboard display. However, when we try to use these new dates when configuring the Scheduling screen, AR won't let us choose them from the drop down in which they are displayed. Instead, it gives this warning: "Make sure to add this date field to all the issue sources of this plan."

What else do we have to do to use these dates?

1 answer

1 accepted

1 vote
Answer accepted
Joshua Sneed Contegix
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 26, 2021

Hi Louis,
Have you tried adding (and populating) the date fields for all issues in the plan source? The logic is that AR can't handle dates for the issues in plan if some of the issues do not have those dates. Alternatively put, the date data set is incomplete and AR can't work with that. Cheers!

Hi Joshua,

We have thousands of issues in this project. Do we have to update ALL of them even if they are done, descoped, etc?

Joshua Sneed Contegix
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 27, 2021

Hi Louis,

Based on the error, yes. I have no experience with this exact error and can't definitively say one way or the other. You can likely bulk update those fields on resolved issues to some date in the past, leaving a smaller subset for accurate date setting. Cheers!

I am currently experiencing the same issue. I don't believe it is a solution as I just did it as explained, I added value for every issue in the project, which is the source of the plan, and it's still the same. 

 

Edit: I also used Filter instead of Project as a source of the plan, where I only filtered for one issue with that field filled in, and the issue is still there. At the same time, I have another project with a different issue type, and I can use that field without any problems. I think it has to be a problem with the project setup you/I are using.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events