Ah! Got it. I can see how that would be an issue! Do you have Fusion already? We are only using the native SSO field mapping in Workfront Setup - so no two-way interaction there. I don't know, but I think that you would be able to set up an event so that it is triggered upon a user's AD info being c...

Hey @Skye Hansen , we use Azure Active Directory for Workfront authentication. We don't pull over manager-team relationships right now, so I can't speak to that. We do pull over Cost Center so we can easily charge CapEx and non-CapEx time to the proper accounts for each team - we insert that into th...

Sure thing - I had to install the app in a Jira instance and start playing with it before I really understood it. Fusion is pricy, for sure. As a workaround, you could create Workfront teams for each Jira project that you want to route to. The app appears to really be pointed at sending work to Ji...

@Kevin Quosig , I think this is a good question for this thread. The Workfront for Jira app does have that limitation: one team/user in Workfront to one Jira project. Once you add a user, you cannot add that user again (see screenshot). This was one of the main reasons why we ended up investing in F...

Similar to the functionality that JIRA supports - you can print your tasks in a card-format (like attached below). I was able to export via Excel and run a mail merge to make this happen, but it would be an awesome native feature. Some items to consider: Customizing data output (i.e. custom data fie...

Currently, we cannot add point estimate values to a bar, pie, line chart/graph. This holds us back from being able to take full advantage of the reporting suite. For example, I report-out on how many points were completed per "Brand" (a custom data field). I have to do this manually, outside of Work...

Another way to ask for this functionality would be to add the ability to run the report with "as of" dates. For example, run the report is if it was a specific date, not just the current date.

This is applicable for some of the work that comes in to one of our Agile teams - most work is fine to be assigned the S/F dates of the sprint, but there are a few items that have a specific due date at some point mid-sprint. We end up adding the actual due date in the title of the task, which is a ...

I know what you mean. This may be a given, but we're just recording the data at this point and looking back at prior sprints to consider how to estimate for the next. Over the next 2-3 months, we'll have a better idea of what "normal" is with a 100% focus. Just creating a custom form with a few data...

Agreed - this would be helpful. Right now, our only way to do this is to manually note various points statistics (i.e. committed points at the beginning of a sprint)