Thanks again.  Unfortunately combining instances isn't an option in this case.

Thank you.  I was hoping there might be some examples of implementations that used some middleware layer, possibly along with Fusion, to connect two Workfront instances.  

Thank you. I agree with you that converting several issues a day to projects would be too much (resulting in too many projects). I like the idea of converting them to tasks, I just wish there were a way to automate this more so it could be done with a single click and that we could default the selec...

Thanks for this reply.  I think for a casual Workfront user, there are too many steps involved in converting an issue to a project, and then adding x number of tasks to a project. The number of tasks varies each time.  It also results in too many projects, so the admin is somewhat messy.  Having eve...

Thank you, that helps, I'm going to test that out.

Wow, thank you for this.  It also worked perfectly for me.  I imagine this would be very valuable to many.  

I agree with this.  For some users, this only happens once in a while, and they get stuck each time trying to figure it out (because they might not have seen it for several months).  

This is very helpful, thank you.  I think this answers my question, because here I can use the Project as my Epic, the Iteration as my Sprint, and then the Stories and any sub tasks or issues fall under the Sprint. Now I can send staff to one location to see the whole hierarchy at once.  Also, it's ...

Thank you for the suggestions.  The boards seem helpful on their own, but don't tie to the Agile Team view (where you can show the burndown chart, assign points, etc.), so they seem disconnected from other Agile features.   Regarding your suggested org structure, it would work to set it up the way y...

We could really use this as well.  Some of our staff spend 20 min each day converting issues to tasks.