Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

GregTr1
GregTr1
Offline

Badges

Badges
0

Accepted Solutions

Accepted Solutions
0

Likes Received

Likes Received
32

Posts

Posts
77

Discussions

Discussions
22

Questions

Questions
55

Ideas

Ideas
22

Blog Posts

Blog Posts
0
Top badges earned by GregTr1
Customize the badges you want to showcase on your profile
Re: Iteration Report: Sum of Work Item Estimates (Points) - Workfront 25-09-2019
@Suzy Park - Grouping by estimate would give you a list of items that shared the same estimate. So, at best, you would get a chart that told you how many tasks were estimated at 1 point, 2 points, 3 points, 5 points, etc. It would still not answer the question: "how many points were completed for my brand?". The real issue is that Workfront does not classify the data attribute "Estimate" as a numerical value, so it cannot be summed, averaged, etc. Ultimately I ended up exporting the data and sum...

Views

60

Likes

0

Replies

0
Re: Workfront / Active Directory integration - Workfront 20-06-2019
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 changed, but not the other way around. Kind of the same way that events work for tasks and other items in FLO construction. So, for example, the logic would be: Set up AD for standard user credentialin...

Views

26

Likes

0

Replies

0
Re: Workfront / Active Directory integration - Workfront 20-06-2019
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 the Address2 field, since we don't need that field for anything else and it's not visible to users on the standard profile view. Just thinking about the Manager field, I would ask Workfront what they wa...

Views

26

Likes

0

Replies

0
Re: JIRA integration - Workfront 05-06-2019
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 Jira to have it be worked on, not the other way around. So if that's your use case (maybe a few development teams get involved in projects and only need to receive work requests) you could use the Workfro...

Views

54

Likes

0

Replies

0
Re: JIRA integration - Workfront 05-06-2019
@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 Fusion - complex routing rules, true two-way sync, Jira can send issues over to Workfront (not just the other way around). Greg Troester CHG Healthcare

Views

54

Likes

0

Replies

0
Re: Help with App Actions in Fusion for Sending a Message - Workfront 05-06-2019
@Allison Sizemore , I'm late to the party but this came across my radar because I'm researching how best to use comments in similar situations. It looks like the issue is that the field noteObjCode has to have a value (thus the 400 error). So if the note is being added to a project, the code is PROJ. Other values that I know of off the top of my head are OPTASK for issue and TASK for task. Also, make sure you've mapped the ID of the object that you want that note added in, be that the project, t...

Views

18

Likes

0

Replies

0
Re: First Fusion Update Event with Jira - Workfront 05-06-2019
@Melinda Layten , I wish I was skilled in the ways of the API, but it's basically Greek to me! Thanks for the suggestion, though. Ultimately, I found that you can reference custom fields in a Jira card update upon a creation event (another screenshot attached). You just click on the "Click or drop here to create" text and you can type in the name of the field you want to update/reference. Then you drop the value in and you're good to go! Also, to solve the problem with issue/task duplication, I ...

Views

31

Likes

0

Replies

0
Re: First Fusion Update Event with Jira - Workfront 28-05-2019
@Josh Porter - one other question for you: have you been able to tie two objects together upon creation? I've been able to do so when tasks are sent from Workfront to Jira by adding an Update Task card after the Create Issue card. However, when I try this from Jira to Workfront, I'm finding that I'm very limited in this regard. (Screenshots attached). Greg Troester CHG Healthcare

Views

31

Likes

0

Replies

0
Re: First Fusion Update Event with Jira - Workfront 23-05-2019
Josh – thanks for the reply! I eventually found the same after posting my question, just haven't gotten back to the forum since. That's exactly what I found by running some reports in Workfront to find that object – I did have the fields associated with a form, so once I plugged in the 26-character identifier, things were jammin'! Are you using Fusion right now? I'm to the point where I'm adding in some complexity to my update FLO and wonder if you've found any key functions to be useful in data...

Views

31

Likes

0

Replies

0
Re: First Fusion Update Event with Jira - Workfront 22-05-2019
Update: I've discovered what my issue was - I was attempting to create an Update Event using the webhook method, which I'm not familiar with. Using the polling method I was able to connect a task and issue together (using a custom field for the Jira Issue ID on the Workfront side and adding a custom field for the Workfront ID on the Jira side). Now I'm running into a 400 error: bad request, missing category: { "message": ": category cannot be null", "statusCode": 400, "_error": true, "method": "...

Views

31

Likes

0

Replies

0
Likes given to
Likes from