Currently you can only set "team assignment to to team" in notifications. Problem is that when assigning a TASK to a team, they may receive that notification WAY too early, and can never receive notification when all predecessors are complete. It would be nice to have TEAM NOTIFICATIONS follow task ...

Yep. that's the way it has worked for years. and it does work in creating forms and when you use the Convert Issue to Project button. However, in FUSION, the convert issue to project card does not operate that way.

Thanks Dale - that's why I thought that the convert issue to project card would map all the data over from the issue to the project. Instead it brings over a set of blank custom forms which then needs to be mapped.

There may already be an "idea" for this, but I couldn't find it. proof reporting in WF is just not acceptable. We need to be able to pull reports grouped by decision, due date, decision date, and other factors. We need to be able to report, group, AND GRAPH by these factors, so the current "fre...

While the parameter object is exposed, it'd be great to be able to filter by custom form. Of course, you cannot group by form since it is a multi-association, but this would really useful when analyzing the parameters, as well as when creating fusion flows where you need to bring in all the paramete...

Not sure if this will go anywhere because there probably aren't enough people following this channel to vote it up to get he required votes, but worth a shot. Currently, when you use fusion to convert an issue to a project, the custom data doesn't come over. No biggie, you can then update the proje...

Currently if you need different durations, you need separate queue topics. In many cases, all is the same for different priorities except the SLA that drives duration. It would be great to set an expectation for our users based on the priority they select.

What a great idea for a configurable setting. Though not all groups track time, this would help gently remind people right while they're in the task in the home space.

Currently if you send a report to a list of users, each user gets the same report delivered. If the report has a $$USER.ID filter, it is ignored. If the person clicks the link on the report, the report is properly filtered. The only option to get the properly filtered report to all the users is ...

Good catch! You can bring it in using text mode if you need this in before it is exposed in the reporting interface. Text mode would look something like this, with the key change to the first line. valuefield=project:owner:namequerysort=project:ownerIDvalueformat=HTMLdisplayname=Project Ownerlinke...