Inherited Budgets missing

Implemented

Follow

New post

Lukas Tynek

• December 06, 2019 16:15
• Edited

Hi,

after last update of "reporting version" we are missing all inherited budgets. 

I have link from Bug to Feature and Feature have link to Epic and this Epic is in Budget. All workitems under epic had Budget of Epic, now all of them are empty.

Is it bug or we have forgot to change something. We see budget only at Epics now.

They are missing in API, and also in time explorer.

When i have tried new api 3.0 we got 500 error on budgets:

DataSource.Error: OData: Request failed: The remote server returned an error: (500) Internal Server Error.
Details:
DataSourceKind=OData
DataSourcePath=https://cisvsts.timehub.7pace.com/api/odata/v3.0/budgets
Url=https://cisvsts.timehub.7pace.com/api/odata/v3.0/budgets

Thanks, Lukas 

 

0

• 

  dev

  • December 06, 2019 16:20

  Hi Lukas,

  This is known issue for the time being, we are working on a fix. 

  Budgets will be corrected soon within several hours, I will update you additionally.

   

  Budgets 500 error will be investigated too.

  Maxim Lutsan

  0

  Comment actions Permalink
• 

  dev

  • December 06, 2019 19:14

  Hi Lukas,

  The first issue is resolved, budget should be properly displayed.

  The 500 error is still under investigation, it will take some additional time.

   

  Maxim Lutsan

  0

  Comment actions Permalink
• 

  Lukas Tynek

  • December 11, 2019 12:12

  Hi Maxim, 

  thanks for your quick reaction. We can see our budgets in time explorer, thank you,  but we cannot still see them in API 

  for example:

  https://cisvsts.timehub.7pace.com/api/odata/TimeExport(StartDate='2019-10-04',EndDate='2019-12-11',PopulateTopParentColumns=null,GroupTimeByDateByUser=null,IncludeBillable=null)?$select=RowID,TFSID,UserEmail,Budget,BudgetHours,DurationInSeconds,TrackedTimeType,TeamMember, ActivityType,ApprovalState,Comment,BudgetClosed, InheritedBudget, UserID&$filter=tfsid eq 77896

  Thanks, Lukas

   

   

  0

  Comment actions Permalink
• 

  dev

  • December 11, 2019 14:49

  Hi Lukas,

  We identified some more issues in new API 3.0 and as we powered 2.1 with new API behind: it can also affect 2.1.

   

  The quickest workaround will be temporarily switching new Reporting feature for your organization and when we fix and roll out everything: we will enable it back. What would you say?
  
  

   

  Maxim Lutsan

  0

  Comment actions Permalink
• 

  Lukas Tynek

  • December 12, 2019 08:27

  Hi Maxim,

  yes, you can rollback the version. Reports loaded from API are important for management. 

  Thanks, Lukas

  0

  Comment actions Permalink
• 

  dev

  • December 12, 2019 08:44

  We rolled it back, but this is cached in the app memory, to reset it please navigate to Settings open any setting and click "Apply" without changing anything.

   

  Maxim Lutsan

  0

  Comment actions Permalink
• 

  Lukas Tynek

  • December 12, 2019 10:17

  Thank you, now seems me everything is working.

   

  Thanks, Lukas

  0

  Comment actions Permalink
• 

  dev

  • January 16, 2020 10:24

  Hello, Lukas!

  We enabled reporting for your organization again. Can you check please if everything OK?

  0

  Comment actions Permalink
• 

  Lukas Tynek

  • January 17, 2020 09:24

  Hi, 

  probably it needs to enable API 3.0.  Everything seems working, except tab reporting.

  

   

  Thanks, Lukas

  0

  Comment actions Permalink
• 

  dev

  • January 24, 2020 09:59

  Hello, Lukas!

   

  Sorry for this. We just enabled API 3.0 for you.

   

  Best Regards

  Dmitrii Vavel

  0

  Comment actions Permalink

Please sign in to leave a comment.