コミュニティアチーブメントバーを展開する。

MartyGa1
MartyGa1
オフライン
タイプ
  • すべて
  • 質問
  • ディスカッション
  • アイデア
  • ブログ
ユーザー投稿による絞り込み
  •    Workfront Questions 2019/07/29
    I've been working with quite a few clients on Workfront to Workfront integrations and the possibilities are endless! Here are some common, yet powerful, use cases. 1) Convert a request to either a project, program, or portfolio. You could extend this a LOT of ways, such as using a custom date field ...

    タイプ

    質問

    表示

    1.9K

    いいね!

    0

    返信

    0
  •    Workfront Questions 2019/02/11
    It sounds like you have your project set to calculate from end date (schedule from .... Start Date, Completion Date), which will calculate backwards from the planned completion date. This will affect the default constraint on your project. If you are using predecessor relationships, you can use the ...

    タイプ

    質問

    表示

    2.8K

    いいね!

    0

    返信

    0
  •    Workfront Questions 2019/02/11
    Sorry - missed the second half of the question. I think it has something to do with the database and API calls, but not positive. Parentheses cause problems when not properly trapped and are often not allowed as a database field name. As far as I can tell, these are the only characters not allowed, ...

    タイプ

    質問

    表示

    1.9K

    いいね!

    0

    返信

    0
  •    Workfront Questions 2019/02/11
    Simple answer, no. Parentheses are not allowed as a custom for label or parameter label. Marty Gawry - CapabilitySource

    タイプ

    質問

    表示

    1.9K

    いいね!

    0

    返信

    0
  •    Workfront Ideas 2019/02/07
    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 ...

    タイプ

    アイデア

    表示

    1.1K

    いいね!

    39

    返信

    7
  •    Workfront Ideas 2019/01/21
    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.

    タイプ

    アイデア

    表示

    1.7K

    いいね!

    0

    返信

    0
  •    Workfront Ideas 2019/01/15
    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.

    タイプ

    アイデア

    表示

    1.7K

    いいね!

    0

    返信

    0
  •    Workfront Ideas 2018/12/23
    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...

    タイプ

    アイデア

    表示

    350

    いいね!

    0

    返信

    1
  •    Workfront Ideas 2018/12/23
    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...

    タイプ

    アイデア

    表示

    327

    いいね!

    16

    返信

    0
  •    Workfront Ideas 2018/12/14
    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...

    タイプ

    アイデア

    表示

    1.7K

    いいね!

    14

    返信

    8