Roadmap

[Tata Tatkhashvili]

Hi there, Could you tell me, If is the possibility to count workers in the Jira roadmap? If is any feature to take out this information? 

and the second question is: can we take out information about the date summary? 

[Klára Zikešová]

To the second question, you can create custom nuber field filled by smart values counting this (in automation rule).

[Tata Tatkhashvili]

Hi, Klara,

Thanks for the feedback.

Could you tell me more about this? how can I configure it and where from?

Thanks for help 

[Klára Zikešová]

Hi, can give you two relatively similar examples of using smart values to calculate something. One is reopen count of a bug and another is  adding one day to the date (that testers know when to start testing - when is the increment already in place due to night builds...)

[Jack Brickey]

Hi @Tata Tatkhashvili ,

I assume by "workers" you mean users that are assigned issues. I don't know of any way of showing a count of assignees in the roadmap. You can see the users that are currently assigned issues in the roadmap view by looking at the avatars at the top. Regarding the second question I'm not exactly sure what you're referring to as far as date summary.

[Tata Tatkhashvili]

Hi, Jack. 

Thanks for feedback

I will try to explain the second question: If I started work in epic on 01.01.2022 and finished on 30.03.2022 is there any possibility to count days? How many days did I work?

[Jack Brickey]

Not OOTB within the app. You might consider using excel or sheets. There is a Jira extension that allows you to easily run queries. Excel/Sheets will allow you to calculate # of days.

[Tata Tatkhashvili]

Jack, very thanks <3. If you know this extention name? Could you share? 

[Jack Brickey]

jira-cloud-for-excel-official 

[Tata Tatkhashvili]

big thanks!

[Jack Brickey]

You are most welcome. Note that the solution @Klára Zikešová suggests is a reasonable approach if you want every issue to provide a numerical count of the number of days you have "been working" on something. I'm not a huge fan of this solution for your scenario but it can be made to work. It really comes down to how you wish to access this data and more importantly how often. If you were still trying to figure out the right solution please provide more details as to your use case including accessing the data and the frequency of this as well as how you would like to present the data. It would also help to understand how you define the time. By which you're working on an issue. What I mean by this is that often times a user will work on an issue one day put it down and pick it up a couple of days later. So does that mean they worked on it for a day or maybe three days? I hope this all makes sense.

[Jack Brickey]

BTW, the "reopen" scenario is an excellent use case for the Automation + custom field solution as you can leverage on Dashboards to show the frequency of reopens. 

[Syed Abdul Basit]

You can export the epic data with its start date and end date. Once exported in MS Excel, use the "networkday" function to get the duration excluding weekends and holidays (if any).