timetracking | Version 2 of this plugin supports MantisBT version v2 | Application Framework library

I have solved my problem. I was actually using the old version of my RootRouter.js which had the Home component declared like so:

I see two issues:

1) You're setting the encodedTokenString to be Data instead of a string.

As observed in the comments, it's not entirely clear what you want, but if you want to remove the keys that have values equal to [] or {}, then you could use walk like so:

The solution I have to by pass this problem is to fetch all the worklogs of the target issues, select the last one, and update it with this rest request :

https://{server}/rest/api/3/issue/{key}/worklog/{id}?adjustEstimate=new&newEstimate={minutes}

However that requires that there is at least one worklog that has been added to the issue.

So

Step 1 :

Fetch every worklog using :

https://{server}/rest/api/3/issue/{key}/worklog/

Step 2:

Loop through all worklog to find the most recent one that you are going to update, and retrieve the timeSpentSeconds and id.

Step 3

Update the worklog using this rest request as a PUT request

https://{server}/rest/api/3/issue/{key}/worklog/{id}?adjustEstimate=new&newEstimate={minutes}

with the following body :

{ "timeSpentSeconds":timeSpentSeconds }

note that you have to send back the timeSpentSeconds with the same number it had before the update to ensure the request call works.

Hope this helps anybody with the same problem that I had.

If anyone have a solution that doesn't require updating a previous worklog, feel free to add a new answer.

You can use async and await along with request-promise-native to loop over your objects and get the list of results you wish to have.

You can call the readEstimates function in a express.get( ).. handler as long as the handler is asynchronous (or you can use readEstimates().then(..)).

Now, we will wrap an error handler around the readEstimates call since, this could potentially throw an error.

For example:

There is no built-in function I'm afraid. I just wrote one, which is fully inlineable ad-hoc SQL - but it won't be fast...

You can try this:

req.session will only be available in routes that occur AFTER the session middleware executes (order dependent). And, if the session middleware is only on one router, then that req.session will only be available in routes that that match that router and only after that router runs on a given request.

So, if you want req.session valid across all your routes, the middleware needs to be defined early and in a way that the middleware runs on all possible routes (that you want to use it on), not only in some routers that only run on some paths.

Remember, it is your session middleware that sets req.session on any given incoming request. It has to run on a given request before you want to access req.session.

You don't have to put your session middleware into your startup file directly. You can still put it in its own module, you just have to load that module from the startup file and pass it the app object so it can initialize the global middleware before any of your routes.

Here's an example startup file:

The callback code runs asynchronously from the rest of your method. You need to run the code in each successive callback, or use async/await or promises.

The simplest adjustment with your existing code (freehanded, may have syntax errors):

You have two separate lists: EmployeeDDL and employeeDDLs. You are trying to use employeeDDLs as the data source for your dropdown: