Daria Spizheva_Reliex_ Atlassian Partner

Hi Ryan! In the native Capacity view, allocation is shown per week — there's no toggle to switch it to sprint-level buckets yet. The view follows calendar weeks regardless of your sprint cadence, so for now the workaround people use is mentally mapping two weekly columns to a sprint, which is obviously not great when…

Hi @Lucas Reis! For now, this stays Marketplace territory, same as it was on Server/DC with your old plugin. To be upfront about our side: I'm from the ActivityTimeline team, and we don't have a live timer either. Our approach to the same underlying pain is different: a personal workspace where all your assigned tickets…

Hi! Jira's REST API has no true bulk worklog endpoint. You call the single-worklog endpoint once per ticket. But that's less painful than it sounds; a small script loops through them fine. Here's the setup: Endpoint: POST /rest/api/3/issue/{issueIdOrKey}/worklog — same endpoint for JSM tickets, since they're regular Jira…

Hi Anna! Subtask-to-parent estimate rollup isn't supported in team-managed projects. In company-managed projects the time tracking panel has an "include subtasks" view, but team-managed projects simply don't aggregate estimates up the hierarchy. For workarounds without double-counting: * Keep estimates on subtasks only and…

Hi Tapan! Natively, Jira gives you a few pieces of this, but no single "hours per user" summary. You can see worklogs on individual issues, and JQL like worklogDate >= startOfWeek() will find issues where time was logged — but Jira won't group those hours by person or total them up for you. The built-in Time Tracking…

Hi @Barbara Homer! That per-ticket clicking is a pain a lot of people share — and to be upfront, native Jira doesn't really solve it. Worklogs live on individual issues, so there's no built-in screen where you log the whole week or see your hours summed up in one place. This is exactly what our app, ActivityTimeline, was…

Hi @Devakumar! Jira doesn't have a built-in weekly timesheet. There's time tracking on individual issues (Log work), and you can see worklogs per ticket — but there's no native report that shows a person's or team's week in one grid. That's exactly the gap marketplace apps fill. Our app, ActivityTimeline, is one of them.…

Hi @Karol Peake ! Thanks for the question — and honestly, you're right, the log-work flow in Jira is tedious. Three dots, menu, dialog, submit… for a 5-minute task, that's a lot of clicking. Natively, Jira doesn't have quick +5m / +15m buttons. I'm from the ActivityTimeline team, and to be upfront, we don't have one-click…

Hi @Tahir_Mohammed , Native Jira can help with this: * Card colors on Company-managed boards — go to Board settings → Card colors and select "Colours based on Queries". Then define a JQL query per status (e.g., status = "In Progress", status = Blocked) and assign a color to each. This adds a colored strip to the left edge…

Hi @Max Brüssow , great write-up! "Shadow work" is such an accurate name for this. A few thoughts: * The Sprint Report (not the Burndown) lists all issues added after sprint start with an asterisk (*) — this catches backlog items dragged in mid-sprint, which your JQL misses. * The Burnup Chart shows scope-change events…

Hi @Maryse Dupuy , welcome to the Jira side! This is a very common pain point for teams coming from Asana, so here's what's possible. With native Jira: * In Plans (Advanced Roadmaps), enable capacity management on a board-based team — this works at the Team level, as you found. A known workaround for per-person views is…

Hi @jeroen_wilmes ! I can't speak for Atlassian's roadmap, but the frustration you're describing — Teams with limited practical use, and Jira groups requiring site-admin rights to manage — is something we hear from customers quite often, so you're definitely not alone here. ActivityTimeline may cover the gap on the…

Hi @Rajshree Rangarajan ! Thanks for reaching out. In native Jira, the Timeline view can display issues by their own dates instead of sprint dates. Open your project's Timeline → View settings, and set the date fields to use Start date and Due date (rather than sprint dates). Once these fields are filled in on your…

Hi @Alexander , welcome to the community! You're on the right track using Jira's built-in issue links — the key is a tool that visualizes them properly. ActivityTimeline can help with part of what you're looking for: * Dependency tracking — enable "Track blocked issues" in the configuration, and ActivityTimeline will read…

Hi! Great question — this is exactly the scale where a resource-planning layer on top of Jira starts to pay off. Keeping Jira as the source of truth is the right call, and ActivityTimeline works on top of your existing projects/boards without changing them. Here's a setup we'd recommend: * Cross-project visibility —…

Hi @Radhika Vijji ! Since native Jira only gives you this kind of epic drill-down inside Plans or per-board reports, a marketplace app that works across the whole instance is indeed the way to go — and ActivityTimeline can cover most of what you're describing: * Epic drill-down across boards/projects — the Project Progress…

Hi @Faisal Mehboob ! Great question — there's no single right answer, but a good rule of thumb: create separate projects when teams have different workflows, permissions, or release cycles, and use components/labels within one project when the work shares a process and you mainly need categorization. Many growing teams…

Hi @Cottam_ Oliver _GS_CITLICS_ ! The Calendar view in Jira Cloud currently displays epics using their scheduled date range (Start Date to Due Date). If your objective is to track upcoming epic deadlines, our tool ActivityTimeline can help here: Milestones Panel — enable Configuration → Timeline Panel → Events → "Display…

Hi @Rukmini Ponnoli ! A few things to check, because "no permission" here usually comes down to one of three causes. 1. Your Jira plan tier. Individual capacity planning is only available on Jira Premium and Enterprise. If your site is on Free or Standard, the feature simply isn't there — no permission change will surface…

Hi @Alexander ! Out of the box, Jira Software Cloud doesn't have a resource utilization report — native reports (Burndown, Velocity, Sprint Report) focus on issue progress, not on people's capacity vs. allocated hours. For utilization you'll need an app. We'd recommend our tool ActivityTimeline — it's built exactly for…

Hi @Goran Stoyan , Plans is genuinely good at sequencing epics and showing dependencies, but its capacity model assumes that everything consuming a team's time exists as an estimated issue inside the plan. Operational work usually doesn't, so the forecast drifts optimistic. On the three options you listed, briefly: 1.…

Hi @Antoaneta Iskra and welocme! This is a common setup, and it's basically what ActivityTimeline (a Jira app we build) is designed for. * Mixing story points and hours: Keep story points on your stories for velocity, hours on sub-tasks. AT lets you set a Story Point → Hours conversion factor (global or per-project) so…

Hi everyone, Great question — this is actually one of the most common pain points we hear from distributed teams, so happy to share how ActivityTimeline handles it (I'm on the AT team). A few things that should cover what you're looking for: Working hours per person You're not locked into a global 8h/day default.…

Hi @Tracey Formilan , This is expected Jira behavior. If your timeline is based on the Sprint field, Jira only shows the current (or last assigned) sprint for an issue — it doesn’t display multiple sprints for the same item. So if a task spans 2–3 sprints, Jira will still show it in just one sprint on the timeline. What…

Hi , Jira can support basic capacity planning natively through sprint planning, issue estimates, and Plans, but it has important limitations like limited visibility into individual workload across multiple projects, no proper availability management (vacations, holidays, non-project work), difficult cross-team resource…

Jira doesn’t natively provide a centralized way to manage your personal schedule and log time from one single workspace but our app, ActivityTimeline, does.

Hi @Tolga Tapan, I’m writing to provide an update on your recent support request. Our technical team is currently troubleshooting the issue. It appears the current limitations within the Free Jira tier regarding billing specifications are contributing to the delay. Expect a detailed update from our Customer Success team…

Hi @Nic H_ , you’re absolutely right — just counting “In Progress” tickets doesn’t tell the full story. Three big tasks can be heavier than eight small ones. What you’re really looking for is a capacity view over time per person, not just a status report. Jira’s built-in gadgets won’t handle that well (especially without…

Hi @Amit Singh welcome to the Community! Custom dashboards in Jira can definitely get confusing. If you’re looking for something more advanced around resource planning, cross-project workload visibility, or capacity management, consider ActivityTimeline, a plugin our team is created specifically for these needs. It adds a…

Hello @Pepik Kaaali! Yes, there is a Cloud alternative that should cover what you need from the TTB plugin. We created ActivityTimeline for Jira Cloud specifically for this kind of capacity planning and workload visualization. It handles the core functionality you're looking for: you can define individual capacity for each…