Auto Scheduler - Disable and Heirarchy

[Suresh]

I am planning to use the portfolio for Jira for planning the roadmap across squads. The squads are currently planning the roadmap in excel, but maintaining epic > story in jira and executing them in sprints. I noticed that auto scheduler is so powerful, if this is exposed to the team members .

1. how do we provide access control to the team members or is there a way to suppress this option until the team gets more familiar with portfolio for jira

2.portfolio maintains a filed for start date and end date for planning the epic or story. once the story is planned, by entering the start and end date in portfolio, does these fields be editable in user story. how to maintain the planning when portfolio has start and end dates while story has date fields which is separate

3. portfolio has the heirarchy as intiative, epic, story, is there a possibility to include a workflow state say assigned, design in progress, dev, testing as heirarchy and do the planning using portfolio

[Joseph Chung Yin]

@Suresh -

In Advanced Roadmaps for Jira (formally known as Portfolio for Jia), you can control who can have access to this tool via Jira Administration > Manage Apps, then access the "Advanced Roadmaps for Jira" - Advanced Roadmaps Permissions.  

In regards to Auto Schedule option, it will be up to each plan editor to use it or not.  However, if it is used, the tool will give you the option to commit the changes or not back to your Jira project(s).  There is no option to disable it.

In regards to start/end dates, each plan can choose the fields in Jira to control the start/end date to be used.  By default, it is using Target Start and Target End date fields.  You can enabled them by setting up the fields in each of your Jira Project's screen configurations.  In the previous Live Plan UI, it is using the Fix Version's Start and End dates fields.

Lastly, WF is not controlled by the tool.  You can customize the WF for each issue type used within your Jira project(s).  So WF and Hierarchy configurations are two separate things. 

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.