We added what we needed via custom fields on the task level.

Thanks for putting this together, Alison. It was helpful to see it in action. After the Video, my scrum master and I reviewed some topics and ideas. I know there was some chatter about another more indepth one based on some topics generated from this video. Our initial thoughts: In the people page, ...

I agree with the Resource Planner piece. How this all integrates with the projects, rollups to the portfolio, and how we can plan. I've started putting ROI against projects. It would be great to see how others are doing this and nuggets of wisdom that have been helpful. I feel like we have just scra...

That is what I ended up doing. It would be cool to have something like that where we could merge projects. Unfortunatly, the updates were made on the project level and not on the task level. I just cut and pasted as well there. Brady Robinder Comcast West Division Winning the West as One

It's been a day and I'm pretty sure I can't do what I want to do with out an act of kindness. I have two projects. Project A and Project B and we have determined they are essentially the same project. I now want to merge them into the same project. They have updates and cool stuff attached to both o...

A request from my team - We want to know how many Tasks/Issues are added to the iteration during the course of the iteration. Has someone cracked this nut? I'd like to understand how scope creeps in the iteration. We can see it on the burndown, but need the report to know which ones or a view, etc. ...

Totally Digging the buttons. Brady Robinder Comcast Corporation - West Division

You can do it, but you have to make the status available for everyone across the entire instance as a default and locked status. It's not a clean way of doing it as Kanban and Agile teams work through task status differently. Upvote the agile one as well as it is the same issue.

It's like this for Agile too. There is another idea out there and I would upvote that one as well. https://support.workfront.com/hc/en-us/community/posts/115001903028-Statuses-don-t-have-to-be-locked-system-wide-to-appear-on-a-specific-team-s-agile-board

I would love the ability to use a group's status instead of a system status for this. Using a system status seems like an architectural miss in the software as you are running both waterfall and agile projects and need the ability to each methodology.