Hi to everyone,
I am trying to configure my Plans scheduling so as to use custom date fields as a basis. I am JIRA Administrator as well as Advanced Roadmaps admin, however, I have one plan where I am able to define my start date out of several possibilities:
and some where it doesn't work although the custom fields are on all screens and also added as custom fields within the plan:
I'm obviously missing something, but I don't get behind it. Any ideas?
Thanks in advance,
Alessa
Hi @Alessa Jaeger _LSY_ ,
I'm going to assume that these plans are configured with different issue sources and that for the plan with more options your issue sources include projects configured to use the listed custom fields, but for the plan with fewer options the projects configured don't have any date type custom fields?
Could you investigate and let me know if that is the case. All projects included in the plan will need to have access to the same custom fields for them to be an option.
Regards,
Dave
Hi @Dave ,
For the plan where I don't can't set the date fields as wanted, the issue source is only one kanban board with JQL "project = XX AND (issuetype in (Epic, Story, Bug) AND Team = YY OR issueFunction in subtasksOf("project = XX AND Team = YY and issuetype in (Epic, Story, Bug)")) ORDER BY Rank ASC
I want to use the custom date fields "planned start" and "planned end". I set them to all screens within project XX for issue types Epic, Story and Bug (also visible in field configs).
I was wondering if it may be due to the rather complicated JQL that advanced roadmaps is missing on those fields....
Best regards, Alessa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Alessa Jaeger _LSY_ - so just to confirm, you can see (and set) those "Planned Start" and "Planned End" fields in the issue screens for issues from all the projects that are loaded into the plan?
Regards,
Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Dave ,
I actually found the error - the "issuefunction in subtasksOf" fetched ALL subtask issue types, although we only use one. For those, I didn't add the date fields to the screens.
Thanks for your effort! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.