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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,534
Community Members
 
Community Events
184
Community Groups

Problem using custom date fields in Advanced Roadmaps

We are starting to use Advanced Roadmaps and are bringing in issues from a small number of projects in our system, but are having problems in the "Scheduling" configuration tab when trying to select the custom date fields we want to use.

To elaborate & provide specifics, we have a large number of different issue types and screen schemes across our projects.  However, for our minimal Advanced roadmaps plan, we have an issue source of a filter that brings in only epics from a single project (i.e. "project = XYZ AND issuetype = Epic").  We have a custom date fields called "Plan Start Date" and "Play End Date" (which have also been added in the "Custom fields" section of our plan's config).

1. If we configure the "Plan Start Date" field and set its applicable issue types to be just Epics, we're unable to select to use this field in scheduling for our plan - we get the message of "Make sure to add this date field to all the issue sources of this plan" (regardless of our plan's displayed hierarchy being set as "epic" to "epic").

2. If we then configure this custom field and set its applicable issue types to be "Any Issue type", then we can now select to use this field in scheduling for our plan.

3. If we configure this custom field to update the applicable issue types, but now manually select all but one of the issue types (the one excluded doesn't seem to matter, and most of the issue types in our system aren't used within our example "XYZ" project's issue type scheme), then we're again unable to select to use this field in our plan scheduling.

 

So I guess my question is - for custom date fields to be selectable in the Advanced Roadmaps "Scheduling" config, do these fields need to be configured to be associated with all issue types in the system, regardless of which issue types are associated with the issue sources?  (I'm hoping we don't have to add these custom fields to all issuetypes in the system if we don't have to, although we may be able to workaround this with careful config management of screen schemes if we have to).

Thanks!

1 answer

0 votes
Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 17, 2023

Hi @Andrew Fisher

I feel this could correspond to the following bug:

While it is targeted to Cloud the content is the same. In case this is what you are seeing also, I would suggest to bookmark the bug report to keep track of the progress.

Cheers,
Daniel

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events