Custom field not accessible through API

[Fredborg_ Bo _EMR_MSOL_RYDK_]

Hi,

I'm using the Advanced Brundown Chart add-on from Agilis.

I have create two custom number fields OE and ETC.

OE is updated daily by Automation as a copy of Original Estimate.

ETC is updated daily by Automation as a copy of issue.timetracking.remainingEstimateSeconds

Now, the problem is that both OE and ETC can be selected as known fields for the qurey setup in the the burndown chart, but only chart based on OE works in practice. Charts based on ETC only shows current/latest value for all dates in the chart. Burndown chart inserted for a single task, based on ETC.

Agilis suggests OE is available in our API whereas ETC is not and I need to update our API??

Please advice. 

[Tomislav Tobijas]

Hi @Fredborg_ Bo _EMR_MSOL_RYDK_ ,

As you have both fields of the same type + you're pulling the same values for each field (seconds from time tracking fields—Original estimate and Remaining estimate) I don't see what else you can really do here 👀

When you say 'our API', what exactly do you mean by that?

Also, from the burndown chart, it appears that you're displaying metrics based on Story points rather than estimations in seconds, minutes, or days...?

I've never used this app, but I'm guessing Ideal is/should be Original estimate and Real is Remaining estimate 🧐

Also, you've tried reaching out to vendors' official support for assistance and they've said you need to "update API on your end"?

Cheers,
Tobi

[Fredborg_ Bo _EMR_MSOL_RYDK_]

Hi Tobi,

Thank you for your reply.

I'm not sure what is ment by "our API", but I assume the data Original Estimate and Remaining Estimate etc. is accessible/exposed by some internal Jira API/Query for being accessible by these 3rd party add-on providers, e.g. for this "Advanced Burndown Chart". 

The chart gives me two options, to show either issue count or story points. I have experienced that storypoints simply just means a field with numbers (Number Field) of an issue.

Both fields are available at the same screens, context and projects. 

I'm thinking the problem is a simplified way the tool treats data (field values):

I think the two data set Original Estimate (OE) and Remaining Estimate (ETC) should be treated in two different ways.

OE is by nature constant, and the burndown chart works as it basically shows when tasks are closed.

ETC is different. here the value ETC it self changes, which should be the input to the burndown chart - but the chart simply just looks at current value and draws the burndown based on this and the status (open vs. done).

Does this sound plausible?  

Thanks, Bo

[Fredborg_ Bo _EMR_MSOL_RYDK_]

It turns our the Advanced Burndown Chart is not able to solve what I'm looking for.