@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...
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 Jira...
@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...
@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...
@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 h...
@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...
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
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...