Marking actual start and end date of the task that is done by outsources (non jira user).

[Vera Valshonok]

I am looking for the best way *to follow and mark in the jira tasks) of the actual start and end date for working on the task by the outsourcer (non Jira user) for the future statistics.

[Emre Toptancı _OBSS_]

Hello @Vera Valshonok ,

If the users you speak about are non-Jira users, that means they won't have an option to update the issue themselves. Some other user (a real Jira user) will have to feed that data to the issue. This could be done by introducing two custom date fields and updating them manually or you can make one of your real Jira users to move the issue to different statuses reflecting the progress of the work done by the non-Jira user.

Not really a feasible option but it is worth mentioning that you can enable "anonymous" access and edit rights to your project. In that case everyone who can access your jira URL will be able to modify your issues. Thu,s your non-Jira users will be able (based on your anonymous permissions) to edit the custom date fields or transition the issues. In this scenario, you won't be able to limit WHO CAN see, edit, transition an issue because all non-Jira users will have permissions on all issues. Additionally you won't be able to see WHO DID something because once again everyone will be doing things anonymously. As I said, I don't think this is a feasible solution but at least it is technically possible.

If you choose to make your real Jira users progress the issues and do the reporting based on issue transition dates, our app Time in Status can help you with reporting those.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can calculate averages and sums of those durations and count grouped by issue fields you select. (For example see the total InProgress time per Epic). You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time.

 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
• Export your data as XLS, XLSX or CSV.
• Access data via REST API.
• Visualize data with various chart types.

https://marketplace.atlassian.com/1211756

EmreT

[Bloompeak Support]

Hi @Vera Valshonok ,

If you use statuses to differentiate non-jira user assignments, you can use status transition dates. Our team at Bloompeak developed Status Time app which provides reports on how much time spent in each status as well as status entry dates and status transition count.

Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project).

Here is the online demo link, you can see it in action and try. Hope it helps.

[Rudy Holtkamp]

Hi @Vera Valshonok ,

I think you should elaborate a bit more on that. E.g. your use case.

In general you can create custom fields called 'start date' and 'end date'. I do see the 'due date' field often used, but more in the sense of an expected end date and not an actual end date. And the created date is also used as start date, but again this might not be your actual start date.