--- language: "en" --- # ActivityTimeline ## ActivityTimeline ActivityTimeline add-on helps organizations to better plan and manage teamwork, schedule events, vacations, bookings, track workload, generate timesheets and ot... [Get started →](https://help.activitytimeline.com/at/admin-quick-start-guide.md) ### Featured articles * #### [Certified Professional Course](https://help.activitytimeline.com/at/course.md) To help you harness the full power of ActivityTimeline, we created the ActivityTimeline Administrator Guide: Mastering Resource Planning and Time Tracking. Why... * #### [Admin Quick Start Guide](https://help.activitytimeline.com/at/admin-quick-start-guide.md) ActivityTimeline can be configured in different ways depending on how your organization plans work, manages teams, and tracks time in Jira. This Quick Start Gu... * #### [High-Level Overview](https://help.activitytimeline.com/at/high-level-overview.md) ActivityTimeline helps teams plan work, track time, and understand performance --- all in one place. It gives you a complete picture of: what work is planned, wh... ### Documentation * #### [Getting Started](https://help.activitytimeline.com/at/getting-started.md) * [High-Level Overview](https://help.activitytimeline.com/at/high-level-overview.md) * [Basic Concepts](https://help.activitytimeline.com/at/basic-concepts.md) * [Admin Quick Start Guide](https://help.activitytimeline.com/at/admin-quick-start-guide.md) * [User Quick Start Guide](https://help.activitytimeline.com/at/user-quick-start-guide.md) * [Certified Professional Course](https://help.activitytimeline.com/at/course.md) * [1 more pages](https://help.activitytimeline.com/at/getting-started.md) * #### [Planner: Resource \& Capacity Planning](https://help.activitytimeline.com/at/planner-capacity-planning.md) * [Planner Interface \& Navigation](https://help.activitytimeline.com/at/planner-interface-navigation.md) * [Users \& Teams in Planner](https://help.activitytimeline.com/at/users-teams-in-planner.md) * [Workload Indicator](https://help.activitytimeline.com/at/workload-indicator.md) * [Planning \& Scheduling Jira Issues](https://help.activitytimeline.com/at/operations-with-jira-issues-in-activitytimeline.md) * [Issues Panel on Planner](https://help.activitytimeline.com/at/issues-panel-on-planner.md) * [8 more pages](https://help.activitytimeline.com/at/planner-capacity-planning.md) * #### [Timesheets \& Time Tracking](https://help.activitytimeline.com/at/team-timesheets.md) * [Personal Workspace \& Time Tracking](https://help.activitytimeline.com/at/individual-workspace.md) * [Progress Timesheets](https://help.activitytimeline.com/at/progress-timesheets-track.md) * [Timeline Timesheets](https://help.activitytimeline.com/at/timeline-timesheet-track.md) * [Detailed Timesheets](https://help.activitytimeline.com/at/detailed-timesheet-track.md) * [Alignment Timesheets](https://help.activitytimeline.com/at/alignment-timesheets.md) * [2 more pages](https://help.activitytimeline.com/at/team-timesheets.md) * #### [Finances - Cost \& Revenue Tracking](https://help.activitytimeline.com/at/finances-cost-revenue-tracking.md) * [Getting Started with Finances](https://help.activitytimeline.com/at/getting-started-with-finances.md) * [Basic Concepts \& Terms: Finances](https://help.activitytimeline.com/at/basic-concepts-terms-finances.md) * [Financial Configuration Overview](https://help.activitytimeline.com/at/financial-configuration-overview.md) * [Financial Reports](https://help.activitytimeline.com/at/financial-reports.md) * [Finances in Practice: Common Scenarios](https://help.activitytimeline.com/at/finances-in-practice-common-scenarios.md) * [1 more pages](https://help.activitytimeline.com/at/finances-cost-revenue-tracking.md) * #### [Reports \& Analytics](https://help.activitytimeline.com/at/reports-analytics.md) * [Planning Reports and Charts](https://help.activitytimeline.com/at/resource-reports-and-charts.md) * [Project Reports and Charts](https://help.activitytimeline.com/at/project-reports-and-charts.md) * [Leave \& Event Reports](https://help.activitytimeline.com/at/leave-event-reports.md) * [Bookmark Reports](https://help.activitytimeline.com/at/bookmark-reports.md) * [ActivityTimeline Reports as Jira Gadgets / Widgets](https://help.activitytimeline.com/at/activitytimeline-reports-as-jira-gadgets-widgets.md) * [1 more pages](https://help.activitytimeline.com/at/reports-analytics.md) * #### [Planning and Time Tracking Scenarios](https://help.activitytimeline.com/at/planning-and-time-tracking-scenarios.md) * [Scenario: Plan \& Rebalance a Sprint](https://help.activitytimeline.com/at/scenario-plan-rebalance-a-sprint.md) * [Scenario: Manage Shared Resources](https://help.activitytimeline.com/at/scenario-manage-shared-resources.md) * [Scenario: Forecast Future Capacity](https://help.activitytimeline.com/at/scenario-forecast-future-capacity.md) * [Scenario: Reserve Team Capacity](https://help.activitytimeline.com/at/scenario-reserve-team-capacity.md) * [Scenario: Review \& Approve Timesheets](https://help.activitytimeline.com/at/scenario-review-approve-timesheets.md) * [1 more pages](https://help.activitytimeline.com/at/planning-and-time-tracking-scenarios.md) * #### [Administration, Integrations \& API](https://help.activitytimeline.com/at/administration.md) * [REST API Documentation](https://help.activitytimeline.com/at/rest-api.md) * [Main Configuration](https://help.activitytimeline.com/at/configuration-settings.md) * [Team Management](https://help.activitytimeline.com/at/team-management.md) * [Project Management](https://help.activitytimeline.com/at/project-management.md) * [User Management](https://help.activitytimeline.com/at/user-management.md) * [8 more pages](https://help.activitytimeline.com/at/administration.md) * #### [Release Notes](https://help.activitytimeline.com/at/release-notes.md) * [ActivityTimeline Migration to Atlassian Forge](https://help.activitytimeline.com/at/activitytimeline-migration-to-atlassian-forge.md) * [What's New in ActivityTimeline Cloud](https://help.activitytimeline.com/at/whats-new-in-activitytimeline-cloud.md) * [Latest Release Notes](https://help.activitytimeline.com/at/latest-release-notes.md) * [Release Notes Archive](https://help.activitytimeline.com/at/release-notes-archive.md) * #### [Common Questions \& Answers](https://help.activitytimeline.com/at/customer-q-a.md) * [FAQ -- Planner](https://help.activitytimeline.com/at/customer-q-a-plan-main-dashboard.md) * [FAQ -- Issue Panel \& Filters](https://help.activitytimeline.com/at/customer-q-a-plan-issue-panel-filters.md) * [FAQ -- Custom events](https://help.activitytimeline.com/at/customer-q-a-plan-custom-events.md) * [FAQ -- Workspace](https://help.activitytimeline.com/at/customer-q-a-work-my-workspace.md) * [FAQ -- Timesheets](https://help.activitytimeline.com/at/customer-q-a-track-team-timesheets.md) * [9 more pages](https://help.activitytimeline.com/at/customer-q-a.md) --- language: "en" --- # 3rd Party Integrations ActivityTimeline supports integrations with other Atlassian Marketplace apps and external tools that are not installed directly in Jira. Many integrations are available out of the box because ActivityTimeline can reuse Jira fields, issue links, hierarchy fields, and other Jira data already available in your instance. Some integrations require additional configuration, such as API tokens, Atlassian credentials, or integration-specific settings. Use the pages below to learn how ActivityTimeline works with Tempo Timesheets, Jira Teams, calendar integrations. * [Integration with Tempo Timesheets (Cloud)](https://help.activitytimeline.com/at/integration-with-tempo-timesheets-cloud.md) * [Import Jira Teams](https://help.activitytimeline.com/at/import-jira-teams.md) * [Integrating with Google Calendar - Export \& Import](https://help.activitytimeline.com/at/integrating-with-google-calendar-export-import.md) * [Integrating with Outlook Calendar - Export \& Import](https://help.activitytimeline.com/at/integrating-with-outlook-calendar-export.md) --- language: "en" --- # Access Management in Finances Access Management allows budget owners to control visibility and editing rights for specific financial trackers. This ensures that sensitive salary information or project costs are only accessible to authorized personnel while facilitating collaboration across the management team. ![image-20260420-140908.png](https://help.activitytimeline.com/__attachments/a_cc5cd64dc735958b0aaf30af2001633eeeddb707cc2ce52672d58cf5cf99635f/image-20260420-140908.png?cb=231535de34c7725f3702cc4323c42078) ## Understanding Financial Roles Every budget in ActivityTimeline has a defined hierarchy of access. Permissions are assigned at the budget level, meaning a user may be an **Administrator** on one project budget while having **Read-Only** access to another. ### 1. The Owner (Budget Manager) The **Owner** is the individual who created the budget. * **Immutability:** The ownership of a budget is fixed and cannot be altered once the budget is created. * **Exclusive Rights:** The Owner is the only person with authority to manage permissions. Only the Owner can add or remove users from the **Administration** or **Read-Only** lists. * **Full Control:** Has full access to all reports, configurations, labor rates, and manual transactions. #### 2. Users (Administration) Administrative access is designed for co-managers who need to maintain the budget's data. * **Capabilities:** Can view all reports and transactions, and **edit all configurations** (Labor Rates, Allocations, Scope, Tracking Settings). * **Restriction:** Administrators **cannot** manage permissions or share the budget with other users. This remains the exclusive right of the Owner. #### 3. Users (Read-Only) Read-Only access is ideal for stakeholders who need to monitor project health without altering the financial setup. * **Capabilities:** Can view all three financial reports (Summary, Budget vs. Spend, Detailed Financial) and all underlying transaction data. * **Data Extraction:** Read-only users have the authority to **Export to Excel** from the reports, allowing for offline analysis. * **Restriction:** They cannot access the "Edit" configuration pages or modify any rates, targets, or transactions. ### Permissions Matrix |------------------------------|-----------|--------------------|---------------| | **Feature** | **Owner** | **Administration** | **Read-Only** | | View Financial Reports | ✅ | ✅ | ✅ | | View Detailed Transactions | ✅ | ✅ | ✅ | | Export to Excel | ✅ | ✅ | ✅ | | Edit Budget Configurations | ✅ | ✅ | ❌ | | Add/Edit Transactions | ✅ | ✅ | ❌ | | **Manage Access \& Sharing** | ✅ | ❌ | ❌ | ### Jira Permission Mirroring (Security Perimeter) The Finances module strictly adheres to your organization's Jira security protocols. Even if a user is granted access to a budget in ActivityTimeline, their visibility is governed by the **"Reuse Jira permissions per Project"** or **"per Issue"** configuration. * **Logic:** The system draws a "fence" around the budget's scope. If a user does not have permission to view a specific Jira project or issue, the financial data (worklogs and associated costs) for that project/issue will be hidden from them within the Finance reports. * **Impact:** This ensures that financial visibility never bypasses the core access levels established within Jira itself. > ***Note:*** *Access management is configured individually for each budget. To grant access, navigate to the specific budget, click* ***Edit*** *, and select the* ***Access management*** *tab in the left-hand menu.* --- language: "en" --- # ActivityTimeline app on Jira DC behind a Proxy server If you run Jira DC nodes behind a proxy server and have any of the following Jira DC node startup parameters then this article applies to your configuration: -Dhttp.proxyHost -Dhttp.proxyPort -Dhttps.proxyHost -Dhttps.proxyPort It is required to configure **-Dhttp.nonProxyHosts** and **-Dhttps.nonProxyHosts**Jira node startup parameters for the app to work correctly in this environment configuration. So that Jira nodes do not go through the proxy server when communicating with each other internally (because the proxy host most likely returns an error code as it does not "know" the internal hostnames). Please follow the following steps to configure **each** Jira DC node. **​Steps:** **1.** Open*\/bin/setenv.sh file* (Linux) or *\/bin/setenv.bat* file (Windows) for editing. **​2.** Find the location where you have any of these parameters: *-Dhttp.proxyHost -Dhttp.proxyPort -Dhttps.proxyHost -Dhttps.proxyPort* **3.** Add -Dhttp.nonProxyHosts **and** -Dhttps.nonProxyHosts parameters with the list of **all**Jira node hostnames (Jira DC with 3 nodes in this example): Example: -Dhttp.nonProxyHosts=node1_hostname\\\|node2_hostname\\\|node3_hostname -Dhttps.nonProxyHosts=node1_hostname\\\|node2_hostname\\\|node3_hostname If you already have this parameter then please just add all those Jira nodes' hostnames to the existing list after**\\\|**symbol. Please note that hostnames are separated with an escaped pipe symbol: **\\\|** **4.** Save the file and restart the Jira DC node. **5.** Repeat the same procedure for every other Jira DC node (2 remaining nodes in this example). This should solve the inter-node communication issue. If the issue still occurs or you are experiencing some other problem that is not described here, please don't hesitate to contact our team at [support@reliex.com](mailto:support@reliex.com). --- language: "en" --- # Set ActivityTimeline as Jira’s Time Tracking Provider ## Overview If your organization tracks worked time, the final recommended setup step is to configure **ActivityTimeline as your Jira Time Tracking Provider**. This replaces Jira's default time tracking dialog with ActivityTimeline's enhanced worklog experience, allowing users to log time more efficiently while giving managers additional visibility into worklogs. ## Set ActivityTimeline as the Time Tracking Provider To change your time-tracking provider, follow these steps: 1. Navigate to **ActivityTimeline Configuration → Timesheet Config** 2. Under **Jira Time Tracking Provider** choose **ActivityTimeline** → Click **'Update'** ![CleanShot 2026-07-06 at 00.26.48@2x-20260705-212706.png](https://help.activitytimeline.com/__attachments/a_925a9c2ee3c71ebd8098dfb3ef370b736c5741a9ad793906f7e7492932100f6c/CleanShot%202026-07-06%20at%2000.26.48@2x-20260705-212706.png?cb=d2c214c94d8d190d8f994a5e84ec4bbf) ## Logging Time from a Jira Issue After ActivityTimeline is configured as the Time Tracking Provider, users can log work directly from the Jira issue page. There are two ways to open the ActivityTimeline Log Work dialog: 1. Click on the **'Actions' icon** located at the top right corner of the issue page → Choose the **'Log work'**option. → The ActivityTimeline Log Work dialog will then open. ![2-20240911-075658.webp](https://help.activitytimeline.com/__attachments/a_6a90b72e893d2ff398efaf663b1664d599ac467a874fc90609a5f6b935231f68/2-20240911-075658.webp?cb=06e2fd3faf46d4638b1e890f7671c307) 2. Starting From V.9.9.4 Click on the show 'Worklogs' tab → Then click 'Log Work' or on a timer icon to log time: ![CleanShot 2024-12-23 at 14.03.15@2x-20241223-120344.png](https://help.activitytimeline.com/__attachments/a_a33b5063da6b48f4638796b703b1355571b5e2c6482c2cd65a96ff1458e40684/CleanShot%202024-12-23%20at%2014.03.15@2x-20241223-120344.png?cb=4e057cdd3b966256558b9abaf6e2e6da) ## Benefits of ActivityTimeline Time Tracking Compared to Jira's default time tracking, ActivityTimeline provides several additional capabilities. 1. **Selection of Worklog Categories** : When logging time from a Jira issue page, users can now choose from [different worklog categories.](https://help.activitytimeline.com/at/worklog-categories.md)This makes it easier to organize and understand where your time is going. 2. **Logging Time for Multiple Days**: Users now have the flexibility to log time for tasks that extend over multiple days in a single entry. This functionality is particularly useful for longer tasks, reducing the complexity and increasing the accuracy of time reporting. 3. **Viewing Worklogs in a Table View:** The manager now can see the total time spent on the issue as well as the breakdown per user directly from the Jira issue page. ## What's Next? Your initial ActivityTimeline setup is now complete, and your managers and team members can start planning work, tracking time, and exploring the application's main features. This Quick Start Guide covered the essential configuration required to get started. However, ActivityTimeline offers many additional capabilities that you can configure as your organization grows, including: * advanced planning and scheduling, * timesheet settings and approvals, * workload and capacity management, * reports and analytics, * financial planning and cost tracking (Advanced Edition), * integrations and synchronization settings, * and many other administration options. To explore all available configuration options, continue with the --- language: "en" --- # ActivityTimeline Cloud vs. Server/Data Center Feature comparison Below you can find a comparison of ActivityTimeline's cloud and on-premise versions, so you can easily see which features are available in both versions and what features are only limited to one of the hosting options. | **Functionality** | ****Server,** **Data Center**** | ****Cloud**** | |------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| | Planning Dashboard | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Personal Workspace | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Time Tracking Reports | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Forecasting Reports | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Workload management | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Availability Tracking | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Skills (*Ability to create and manage custom skills in the app)* | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Split task across multiple users | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Vacation / Holiday schemes | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Custom Events *(Overtimes, partial or full time day-offs,* *placeholders, meetings, bookings)* | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Bulk actions *(Schedule, reschedule, assign and un-assign)* | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Ability to log hours on behalf of other users | ![minus](https://help.activitytimeline.com/__attachments/a_8ca4bfe82ba3047e4cfa25d0bbb3a31639201d978ad2d697f284d9be79ae170a/atlassian-minus?cb=b04d1998b2b6fc12820166ffbfbaa231) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | ActivityTimeline's Log Work in Jira issue view | ![minus](https://help.activitytimeline.com/__attachments/a_8ca4bfe82ba3047e4cfa25d0bbb3a31639201d978ad2d697f284d9be79ae170a/atlassian-minus?cb=b04d1998b2b6fc12820166ffbfbaa231) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Export ActivityTimeline's data to MS Outlook \& Google Calendar | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Creation of Jira tasks/projects directly from the app | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Import of Google calendar events to ActivityTimeline | ![minus](https://help.activitytimeline.com/__attachments/a_8ca4bfe82ba3047e4cfa25d0bbb3a31639201d978ad2d697f284d9be79ae170a/atlassian-minus?cb=b04d1998b2b6fc12820166ffbfbaa231) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Chart reports | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Billable / Non-billable reporting in Timesheets | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | REST API | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Milestones Panel | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | ActivityTimeline reports as Gadgets on Jira Dashboards | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.activitytimeline.com/__attachments/a_76d7671065eee9137a7d920340eac82e183c089e09eb6d7b6c6233ba846d122a/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | You can learn more about the comparison between ActivityTimeline Cloud and On-Premises versions in the following article: [Migration of ActivityTimeline from Jira Server/DC to Jira Cloud](https://help.activitytimeline.com/at/migration-of-activitytimeline-from-jira-server-dc-.md) --- language: "en" --- # ActivityTimeline Migration to Atlassian Forge Atlassian is moving Cloud apps from **Connect to Forge** , its current platform for building apps for Jira and other Atlassian Cloud products. As part of this transition, Atlassian will end support for Connect on **January 31, 2027**. You can read more in Atlassian's official announcement: [Getting Ready for Connect End of Support](https://www.atlassian.com/blog/development/getting-ready-for-connect-end-of-support)[.](https://www.atlassian.com/blog/development/getting-ready-for-connect-end-of-support?utm_source=chatgpt.com) ActivityTimeline is already in the process of migrating to Forge and is on track to complete the transition ahead of this deadline. This page provides information about our migration progress, what is changing, and what ActivityTimeline customers need to know. ## Current status The first migration step has been completed, and **ActivityTimeline Cloud** app is currently running in **Connect-on-Forge mode**where some modules are already migrated to Forge and some are still on Connect. We are now working on the final stage of the migration. By **October 30, 2026** , we plan to complete the transition to **pure** **Atlassian Forge**without any legacy Connect modules. ## Do customers need to take any action? **No action is required as of now.** The migration is being handled by the ActivityTimeline team, and customers do not need to manually migrate their data or configuration. You may currently see a **Legacy** or Connect end-of-support notice for ActivityTimeline in Atlassian Administration or Jira. This notice relates to the underlying Atlassian Connect technology that ActivityTimeline is transitioning away from. It does **not** mean that ActivityTimeline is being discontinued. Once our Forge migration is completed and the corresponding Atlassian requirements are met, ActivityTimeline will no longer rely on the legacy Connect framework. You may see an "Update" button on the Jira's Configuration → Marketplace Apps page to manually update the app to the latest version if it was not automatically updated. ## Will anything change? Our goal is to keep the transition as seamless as possible and preserve the existing ActivityTimeline experience. However, because Forge and Connect have significant technical differences, a small number of existing integration points may work slightly differently after the migration. Due to the current limitation of Forge support on Jira mobile app, **ActivityTimeline Log Work action will no longer be available in the Jira mobile app** after the Forge migration, as the required functionality is [not currently supported by Atlassian for Forge apps on mobile.](https://jira.atlassian.com/browse/JRACLOUD-95236) Logging work through ActivityTimeline in Jira on the web will remain available as usual. We will continue to monitor Atlassian's Forge mobile capabilities and intend to restore this functionality once the necessary support becomes available. ## Stay updated We will keep this page updated with the latest migration status and any customer-facing changes. Our current target is to **complete ActivityTimeline's Forge migration by October 30, 2026**(or sooner), ahead of Atlassian's Connect End of Support. If you have questions about the migration or how it may affect your ActivityTimeline environment, please contact our [Support team.](https://reliex.freshdesk.com/support/tickets/new) --- language: "en" --- # ActivityTimeline on Jira Server/DC that is running on Java 11 ActivityTimeline v8.x.x and earlier are compatible with **Java 8**. ActivityTimeline v9.x.x are compatible with both **Java 8** and **Java 11**. ActivityTimeline v10.x.x, v11.x.x, v12.x.x are compatible with **Java 8,** **Java 11** and **Java 17**. ActivityTimeline v12.x.x-jira11 are compatible with **Java 17** and **Java 21**. The previous versions of ActivityTimeline application (before v9.0.0) for Jira Server/Data Center supports Jira Server/DC versions that run on Java 8 only (including the latest Java 8 security fixes). The easiest way to get the old ActivityTimeline app running is to switch Jira to **Java 8**. If Jira Server/DC must run on Java 11 then additional configuration of ActivityTimeline was required to work properly. **Configuration Steps** 1. Install Java 8 on the server where Jira is running. 2. Open *\/plugins/activitytimeline/config/at.properties* file for editing. \ is usually */var/atlassian/application-data/jira* on Linux servers. 3. Add the following line into that file: at.java_home.path=JAVA8_EXECUTABLE_PATH where *JAVA8_EXECUTABLE_PATH* is full path to installed Java 8 executable file. **Examples:** 1. /usr/lib/jvm/jre-1.8.0-openjdk.x86_64/bin/java 2. /usr/lib/jvm/jre-1.8.0/bin/java 3. C:\\\\Program Files\\\\Java\\\\jre8\\bin\\\\java.exe 1. Please note that each back-slash should be doubled for Windows OS based server. 4. Save *at.properties*file. 5. Open a troubleshooting page at the following link and click **Restart** (or **Start)** service button: [++https://\/plugins/servlet/activitytimelineconfig/configuration++](#) ![image-20210223-104640.png](https://help.activitytimeline.com/__attachments/a_847bf0e207882a16864bb054abe3fd652efe2cd473951a60d49f12742b2d0e54/image-20210223-104640.png?cb=0ce089deda3405dc50269bfaa3198e56) This should tell ActivityTimeline to use a different version of Java that for Jira. In this case, Jira will stay on Java 11 while ActivityTimeline will utilize Java 8. In case you are not sure about the reasons, please make sure to [contact our Support Team](mailto:support@reliex.com) --- language: "en" --- # ActivityTimeline Reports as Jira Gadgets / Widgets This documentation outlines the process and guidelines for integrating ActivityTimeline reports as gadgets into Jira Dashboards. This feature aims to enhance productivity and decision-making by providing easy access to vital analytics directly within Jira. ![CleanShot 2026-05-27 at 10.54.35@2x-20260527-075440.png](https://help.activitytimeline.com/__attachments/a_77cc497e0ee1e4ce5821e00c9f3af2b05d892d804cef6e0a4ed7d63905c9ef3f/CleanShot%202026-05-27%20at%2010.54.35@2x-20260527-075440.png?cb=a4772be318234cc3ecec45f7d1c8d53f) ## How to add ActivityTimeline report as a Jira Gadget? It is possible to add reports as Jira gadgets to your Jira gadget the same way you add your standard Jira Gadgets. ++Navigate to Dashobards → Open your dashboard → Click 'Edit' on the top right corner:++ ![2-20240916-132441.png](https://help.activitytimeline.com/__attachments/a_97c94ce8cc0aee11be35edd20c0c5d64800b845fe977b0cfbfd6e41a12e74c32/2-20240916-132441.png?cb=6b025322a445e8b2bdafcc491c565967) ++Click to add a new gadget → Find ActivityTimeline gadget in the list and add it:++ ![3-20240916-132454.webp](https://help.activitytimeline.com/__attachments/a_b63bfcd2955d422beee42a12fc5419ee0a36e45dd45dcc6783a48e24f20dcd84/3-20240916-132454.webp?cb=eef7d13f0d425db7e2f4c601e7f87f0e) ## How to configure automatic refresh? Our gadgets refresh data with the same frequency as all the gadgets on the dashboard. You can configure the frequency in the configuration of each dashboard: ![4-20240916-132441.png](https://help.activitytimeline.com/__attachments/a_e53b4995a0506750ee63b51a32e3306b29798069ac070898caec3abe091330ce/4-20240916-132441.png?cb=c6a928fcc48399e3ea50667fdaa075af) ![5-20240916-132441.png](https://help.activitytimeline.com/__attachments/a_8a5aef69d051092a10e19f5371915fb1b8bc0647fcfe3d5709e702cd98ad7cb9/5-20240916-132441.png?cb=3ad1fd3a86c9432faffe795add8d65e5) You can get real-time data at any time, once you click on the refresh on each individual gadget: ![6-20240916-132453.webp](https://help.activitytimeline.com/__attachments/a_a5058ac2afab1139b9b1242ebc6ef588bd9645d9589dab204f3a376d2719efa5/6-20240916-132453.webp?cb=143432b074bcb8ba66d348f5dce6cffc) ## ActivityTimeline Gadgets and Confluence Now, if an ActivityTimeline report or chart is added as a gadget in the Jira Dashboard, users can click on the link icon and embed it into a Confluence page if needed. [CleanShot 2024-08-08 at 13.22.02.mp4](https://help.activitytimeline.com/__attachments/a_abf6240df954f958de29c96ef8f65a6d78249dbfdcd205f8dd611af780174d3c/CleanShot%25202024-08-08%2520at%252013.22.02.mp4.md?cb=ec13a7d6e73049112a687a57a056aef1) This integration makes it easier to keep all your project-related information consolidated and up-to-date, fostering better collaboration and more efficient project management. ![CleanShot 2026-05-27 at 10.55.21@2x-20260527-075527.png](https://help.activitytimeline.com/__attachments/a_3e38b761ff0fc5eac6d36c6c57e71c2e43fb7cd354cd12970677c881db151dc4/CleanShot%202026-05-27%20at%2010.55.21@2x-20260527-075527.png?cb=44fd7091e95fb0641b223eb44df61795) --- language: "en" --- # ActivityTimeline Team Field for Jira ActivityTimeline allows users to assign Jira issues directly to the **Team Panel** from the Jira issue screen. This is useful when work should be planned at the team level instead of being assigned to a specific individual. ## Configuring the Team Field To enable this integration: 1. Go to **ActivityTimeline Configuration → Jira Integration**. 2. Find the **Team Field** section. 3. Click **Create Team Field**. 4. Enter a name for the Team Field. 5. Click **Submit**. ![CleanShot 2024-05-01 at 13.55.51@2x-20240501-105555.png](https://help.activitytimeline.com/__attachments/a_70cf2ee8c04345b0fb8aa01d2b594d6061ac2152fff7bd789205b7b4fd405692/CleanShot%202024-05-01%20at%2013.55.51@2x-20240501-105555.png?cb=4b3a89e946f65163d96f80478cd4c436) After you click the 'Submit' button, ActivityTimeline will create a new custom field in your Jira and add it to your Jira issue screens. Afterward, the system will update all issues that are currently scheduled on the Team Panel with the corresponding Team field value, this **may take a couple of minutes depending on the size of your Jira instance.** Once the field is created, users can open a Jira issue and select a team in the Team Field to display the issue on the corresponding Team Panel in ActivityTimeline. [3.mp4](https://help.activitytimeline.com/__attachments/a_b661c9674259e11e08d9be2850c7fe702ae578f67b0a73337f59798526e4a6c0/3.mp4.md?cb=4f588112fade2665f3c61ec17d2b5aed) ### How Team Assignment Works When an issue is scheduled on the Team Panel, ActivityTimeline clears the issue assignee and sets the Team Field value instead. This allows the issue to be planned for a team without assigning it to a specific user. ### Important Notes * The **assignee field takes precedence** over Team Field, so if an issue is assigned to both User \& Team, it will be shown on the user's timeline * Team Panel **does not support Issue parts**, hence it's not possible to partially assign a task to the Team \& partially to an individual * Jira instance must allow **'Unassigned issues'**, you can check if your instance allows this in Jira Settings-\>System ![4-20240919-082658.webp](https://help.activitytimeline.com/__attachments/a_e4bc6194d6f887bf5eebdb2a63b7f80bebe6410bbc1a8603bb53271048622d19/4-20240919-082658.webp?cb=11d96c85cdab331080c451696ea679df) * You can 'unlink' the field from ActivityTimeline and the system will no longer try to update it, after this, you can remove the field from your Jira instance. You can do this in ActivityTimeline Configuration → Jira Integration → Unlink: ![5-20240919-082651.png](https://help.activitytimeline.com/__attachments/a_ff12b14af525e2cf987a9f2b2962d87905a06b9f399fa727f1b3247be9d23d47/5-20240919-082651.png?cb=4c60a45cde7dd9719bce7e54774fdf86) You can also learn more about Team Panel here: [Team Panel Workload Modes](https://help.activitytimeline.com/at/team-panel-workload-modes.md) --- language: "en" --- # ActivityTimeline with 3rd party SSO add-ons If you have **any Single-Sign On (SSO) add-on enabled on your Jira Server/DC instance** then you should apply extra configuration to it for compatibility with ActivityTimeline. Basically, you should add a couple of ActivityTimeline app links into the exclusion list of the SSO add-on: /plugins/servlet/activitytimelineconfig/\*,/plugins/servlet/activitytimelineproxy/\*,/rest/activitytimeline/\*,/plugins/servlet/activitytimeline/\*,/plugins/servlet/activitytimeline Below is an example on how to configure a popular EasySSO add-on for Jira. ## EasySSO Below you can find a short guide on how to do it on example of **EasySSO add-on**: 1. Please, go to *Jira* *Administration → Manage Apps → On the left panel click on* ***EasySSO*** *:* ![1-20240912-130904.png](https://help.activitytimeline.com/__attachments/a_687e170c143c69e511171c78837be4319f0ecc790102275291bb808ebf827527/1-20240912-130904.png?cb=7a67958ff1f0758cb2158a5e4489dffe) 2. Add the following string into **Excluded Paths** field: /plugins/servlet/activitytimelineconfig/\*,/plugins/servlet/activitytimelineproxy/\*,/rest/activitytimeline/\*,/plugins/servlet/activitytimeline/\*,/plugins/servlet/activitytimeline ![2-20240912-130904.png](https://help.activitytimeline.com/__attachments/a_69ffcb65793032c6d7dc86b4261a6a01a9ddd274bf3057e05f471f6888c62233/2-20240912-130904.png?cb=a54a851710c92dc79bc9962e455949ae) 3. Click '**Save**'. If the issue still occurs or you are experiencing some other problem that is not described here, please don't hesitate to contact our team at [support@reliex.com](mailto:support@reliex.com). --- language: "en" --- # Admin Quick Start Guide ActivityTimeline can be configured in different ways depending on how your organization plans work, manages teams, and tracks time in Jira. This Quick Start Guide walks administrators through the recommended initial setup --- from Jira integration and team configuration to planning, workload, and time tracking. ## Recommended Setup Order Follow these steps to configure ActivityTimeline around the way your organization plans and tracks work. Each step helps you answer one key setup question, from deciding what Jira data to use to validating the configuration with a real team. ![CleanShot 2026-08-07 at 16.10.56@2x-20260807-131102.png](https://help.activitytimeline.com/__attachments/a_6722c73e824e4fa87acae7d46f694ac2067d46744a9c08e3949e08bebc01ced7/CleanShot%202026-08-07%20at%2016.10.56@2x-20260807-131102.png?cb=2969dff974940669d98dd0ad5458372e) Some settings are required for every instance, while others are optional depending on your workflow. ### **1. How Should ActivityTimeline Use Your Jira Data?** First, decide what Jira data ActivityTimeline should use and how planning should work. * [**Review Project Scope**](https://help.activitytimeline.com/at/project-synchronisation.md) Confirm that the Jira projects you want to manage in ActivityTimeline are active and synchronized. If the correct projects were already selected during the initial setup, no additional changes are required.If a project is deactivated in ActivityTimeline, new changes from that project are no longer synchronized, while previously synchronized data remains available until it is removed. To learn how synchronization between ActivityTimeline and Jira works, visit: [Synchronization](https://help.activitytimeline.com/at/synchronization.md) ActivityTimeline automatically syncs changes from Jira every 10 minutes. If a change you just made in Jira isn't showing up yet, that's expected --- check back shortly, or use a manual **Refresh** if you need it immediately. > ***Why this matters:*** *Project scope determines which Jira issues and worklogs are available for planning, time tracking, and reporting in ActivityTimeline* * [**Review Planning Dates**](https://help.activitytimeline.com/at/map-custom-fields.md) By default, ActivityTimeline uses Jira **Start Date** and **Due Date** for Company-Managed projects. If these are the fields your organization uses for planning, no changes are required. If you use different Jira date fields, map them as the Planned Start and End Date fields in ActivityTimeline. For **Team-Managed projects**, planning dates are configured separately. You can either reuse Jira's standard Start/Due Date fields to keep planning synchronized with Jira, or keep planning dates only in ActivityTimeline. > ***Why this matters:*** *These settings determine which Jira data ActivityTimeline uses and how Jira issues appear and stay up to date in the Planner.* * [**Review Sprint-Based Planning**](https://help.activitytimeline.com/at/use-sprint-start-end-dates-to-automatically-show.md) If your teams plan work in Jira Sprints, ActivityTimeline can automatically place issues on user timelines using Sprint Start and End dates. This behavior is enabled by default, so no additional setup is normally required. Individual Jira Start/End dates take priority over Sprint dates. If you want an issue to follow its Sprint dates, its individual planning dates should be empty or not mapped. * [**Configure Webhooks**](https://help.activitytimeline.com/at/video-example-how-to-use-jira-start-end-dates.md) Add the ActivityTimeline webhooks to ensure issues and worklogs deleted in Jira are also removed from ActivityTimeline. *** ** * ** *** ### **2. Set Up Teams and Users** ![CleanShot 2026-08-07 at 17.24.16@2x-20260807-142421.png](https://help.activitytimeline.com/__attachments/a_12a963f8bbf77c50cf777986e6c0682a6a8d8f8041e27942cedd32b5a31d92c3/CleanShot%202026-08-07%20at%2017.24.16@2x-20260807-142421.png?cb=c079093583d864439d898363e1f8c804) Next, define who you want to plan and how your organization is structured in ActivityTimeline. * [Create teams manually,](https://help.activitytimeline.com/at/create-your-first-team.md) from [Jira Groups](https://help.activitytimeline.com/at/jira-groups-management-in-activitytimeline.md), or [import **Jira Teams** i](https://help.activitytimeline.com/at/import-jira-teams.md)f you already use them. * Assign the appropriate[**roles and permissions**](https://help.activitytimeline.com/at/user-roles-and-permissions.md) to control what users can view and manage. * Configure [**positions and skills**](https://help.activitytimeline.com/at/assign-users-to-roles-positions-and-skills.md) if you use them for staffing, resource search, or team creation. > ***Why this matters:*** *Teams and users form the structure of the Planner, reporting, and capacity calculations.* *** ** * ** *** ### **3. When Are Users Available?** ![CleanShot 2026-08-07 at 17.28.13@2x-20260807-142819.png](https://help.activitytimeline.com/__attachments/a_647eb6adca6241c42f487c0080fea7810ad7d9d4cf44d61610035ec1322ea028/CleanShot%202026-08-07%20at%2017.28.13@2x-20260807-142819.png?cb=7e795d2ff9157b4ec4ab4ed96148c315) Define when users are available for work and how much capacity ActivityTimeline should use for planning. * Assign [Workload Schemes](https://help.activitytimeline.com/at/workload-schemes.md) to define working days and hours. * Assign the appropriate [**Holiday Schemes**](https://help.activitytimeline.com/at/holidays-schemes.md) so public holidays and other organization-wide non-working days are reflected in capacity. If users have different schedules, create additional schemes and assign them individually or through Jira Groups. > ***Why this matters:*** *ActivityTimeline compares planned workload with each user's available capacity. Setting this up correctly ensures that availability, utilization, and overload indicators are accurate.* *** ** * ** *** ### **4. How Should Work Be Assigned?** ![CleanShot 2026-08-07 at 17.18.21@2x-20260807-141829.png](https://help.activitytimeline.com/__attachments/a_e4f738e4bd99ed2df4f4d3a3c2cce71189504463b9d0a85aba9c9307a98a66c0/CleanShot%202026-08-07%20at%2017.18.21@2x-20260807-141829.png?cb=21926aeb1f11aa5fbe2bd095e2435e75) By default, ActivityTimeline uses the **Jira Assignee** field to place issues on the corresponding user's timeline. If your planning process requires more flexibility, you can optionally configure: * [**ActivityTimeline Team field**](https://help.activitytimeline.com/at/activitytimeline-team-field-for-jira.md) --- use it when an issue should be assigned to a team before an individual assignee is known. * [**Issue Collaborators**](https://activitytimeline.atlassian.net/wiki/spaces/AC/pages/54329369/Issue+Collaborators+Multiple+User+Picker+Field) --- use it when several users need to work on the same Jira issue. > ***Why this matters:*** *These settings determine where work appears in ActivityTimeline and whether it is planned for an individual user, a team, or multiple collaborators.* *** ** * ** *** ### **5. How Should Workload Be Calculated?** ![CleanShot 2026-08-07 at 18.17.16@2x-20260807-151724.png](https://help.activitytimeline.com/__attachments/a_362a09b92adc2a026f24d6af9da52e57e416c3126ce4517053e7740086dbb102/CleanShot%202026-08-07%20at%2018.17.16@2x-20260807-151724.png?cb=79eb42679bd9c6befae8d5e64f8da202) Once users, capacity, and assignments are configured, review how planned work should consume that capacity. * By default, ActivityTimeline uses the Jira **Remaining Estimate** to calculate workload. * If your teams estimate work in **Story Points** , you [can configure a Story Points-to-hours conversion](https://help.activitytimeline.com/at/configure-story-points-conversion-into-hours.md) so these estimates can also be used for capacity planning. Hours and Story Points can be used depending on how individual issues are estimated. * For work that should reserve a fixed amount of capacity each day, use a [Daily Estimate](https://help.activitytimeline.com/at/daily-estimate.md). If a Daily Estimate is set, it takes priority over the Jira Remaining Estimate or Story Points for workload calculation. * Finally, choose the [**Workload Calculation Mode**](https://help.activitytimeline.com/at/workload-calculation-algorithm.md) that determines how the issue workload is distributed across its scheduled days. > ***Why this matters:*** *These settings determine how much capacity planned work consumes and how ActivityTimeline identifies available capacity and overloads.* *** ** * ** *** ### **6. How Should Time Spent Be Tracked and Managed?** ![image-20260807-142245.png](https://help.activitytimeline.com/__attachments/a_5e803370e6bcc20db2f04c2773d3e2867f248fc0c3efd87304b10f6ada509fd1/image-20260807-142245.png?cb=3927d14311044557c092bb1f17d69b93) First, decide whether your teams log actual worked time. **If users do not log worked time:** Select **Users do not log worked time** as the [Time Tracking Mode](https://help.activitytimeline.com/at/time-tracking-modes-and-workload-calculation.md). You can then skip the remaining time-tracking and timesheet configuration in this step. **If users do log worked time:** Choose the Time Tracking Mode that matches how your organization plans and tracks work, then review the settings below to define how time should be logged and managed. You can configure: * [**Timesheet rules**](https://help.activitytimeline.com/at/timesheet-config.md) --- for example, whether users can log time on resolved issues, log future or past work, or whether a work description is required. * [**Worklog Categories and Attributes**](https://help.activitytimeline.com/at/worklog-attributes-in-activitytimeline.md) --- if logged time needs to be classified for reporting, billing, or internal work types. * [**Timesheet Approval**](https://help.activitytimeline.com/at/timesheet-approval-and-period-closure.md) --- if submitted time needs to be reviewed by managers or team leads. * **Time Tracking Periods and Period Closure** --- if you need to control when historical worklogs can still be added or edited. * [**ActivityTimeline as the Jira Time Tracking Provider**](https://help.activitytimeline.com/at/activitytimeline-as-time-tracking-provider-in-jira.md)--- if you want users to access ActivityTimeline time tracking directly from Jira. > ***Why this matters:*** *Your time tracking setup determines how actual worked time affects remaining workload and how worklogs are recorded, classified, reviewed, and reported.* *** ** * ** *** ### **7. Is Your Setup Ready to Roll Out?** Start with one representative team and make sure the configuration works as expected before rolling ActivityTimeline out across the organization. Check that: * The required Jira projects and issues are available in ActivityTimeline. * Jira issues appear for the correct users and teams. * Planning dates are correct. * Sprint dates behave as expected, if used. * User working hours and holidays are reflected correctly in capacity. * Team assignments and Issue Collaborators work as expected, if configured. * Workload is calculated and distributed correctly. * A newly created or updated worklog is synchronized correctly. * Time logging restrictions behave as expected, if configured. * The approval process works correctly, if enabled. > ***Why this matters:*** *A short pilot helps identify configuration changes before you introduce ActivityTimeline to the rest of the organization.* *** ** * ** *** ### **Optional: Do You Need Financial Tracking?** If you use the **Advanced Edition** , [configure Finances](https://help.activitytimeline.com/at/financial-configuration-overview.md)to connect logged Jira work with budgets, costs, revenue, and profitability. Start by: * Creating a **Budget** and defining which Jira work it should track. * Configuring **cost and billing rates** so ActivityTimeline can calculate labor cost and revenue. * Setting **Budget Allocations** if you want to compare planned financial targets with actual spend. * Adding **manual transactions** for costs or revenue that do not come from Jira worklogs. * Reviewing the financial reports to track budget consumption, spend, revenue, and profitability. > ***Why this matters:*** *Finances connects the operational work already tracked in ActivityTimeline with its financial impact, helping you understand what work costs, whether you are staying within budget, and how delivery affects profitability* ## Setup Video Watch the video below to learn how to configure ActivityTimeline in under **7 minutes**. --- language: "en" --- # Administration, Integrations & API *This section contains documentation for ActivityTimeline's Cloud and Data Center versions.* User Guide is available [++here++](https://help.activitytimeline.com/at/user-guide.md). ActivityTimeline administrator has permission to administer, change users, and roles, add new projects, synchronize the issues, and change default settings. ## Installation The installation process of ActivityTimeline is identical to most Atlassian Marketplace applications and consists of a few simple steps: 1. Log into your Jira instance as an admin. 2. Click the admin dropdown and choose Apps or on the top Apps on the top menu bar for Cloud → Explore More Apps. 3. Locate ActivityTimeline. ![CleanShot 2024-12-16 at 14.53.40@2x-20241216-125359.png](https://help.activitytimeline.com/__attachments/a_d5e1de409f73f1ca967f31db33d711fcde95ed8cd863fcfd42235b4cf86afb70/CleanShot%202024-12-16%20at%2014.53.40@2x-20241216-125359.png?cb=c6b73bf40e94f46583f5e7ae7c3575fc) 4. Click Try it free to download and install the app. 5. Once installed, click "Configure" button and Setup Wizzard will open: ![CleanShot 2024-12-16 at 14.45.10@2x-20241216-124514.png](https://help.activitytimeline.com/__attachments/a_ac06e39ae40c7e3e15613d5adfd77338ae2eca70d9f4011a282b5586d1f7ad81/CleanShot%202024-12-16%20at%2014.45.10@2x-20241216-124514.png?cb=6eef5ad2164adf81537e51cf6c46e2a8) **For the Data Center version, you also need to select how you would like ActivityTimeline to link with your Jira.** There are two options for running synchronization in ActivityTimeline: 1. Current User: The synchronization will run using the permissions of a selected user, who must have the Browse Project permission for all projects managed in ActivityTimeline. 2. ActivityTimeline Add-on Sync User: ActivityTimeline will automatically create a dedicated user solely for synchronization purposes. If you choose the first option (Current User), please note that if this user is disabled in Jira, the synchronization will stop. To resolve this, a Jira admin with the necessary permissions can re-run the Setup Wizard to assign themselves as the sync user. Alternatively, you can switch to using the Add-on Sync User at any time by navigating to Configurations -\> Setup Wizard. ![CleanShot 2024-12-16 at 14.45.54@2x-20241216-124559.png](https://help.activitytimeline.com/__attachments/a_f9005812fd11a580caa12ea89774059038973dfa425ae242c4d60dfe1d7fb8ba/CleanShot%202024-12-16%20at%2014.45.54@2x-20241216-124559.png?cb=7acdd021848e30b4525596f017a80048) 6. Select Projects to manage in ActivityTimeline and click "SELECT \& PROCEED" button below: ![CleanShot 2024-12-16 at 14.50.22@2x-20241216-125027.png](https://help.activitytimeline.com/__attachments/a_b6777b4e5b08dd2cc191b691405a4df1692747fca52d6913217875f10945da5e/CleanShot%202024-12-16%20at%2014.50.22@2x-20241216-125027.png?cb=744f61adf745ad15f0780263974a1733) 7. Wait a couple of minutes until the system initializes all the necessary data. Click "FINISH" button when the operation is complete. ### Navigating ActivityTimeline Configuration ActivityTimeline settings are managed from the **Configuration** section. At the top of the page, you can switch between the main configuration areas, such as **Configuration** , **Dashboards** , **Teams** , **Projects** , **Users** , **Issues** , **Events** , and **Synchronization**. ![CleanShot 2026-07-07 at 17.25.35@2x-20260707-142601.png](https://help.activitytimeline.com/__attachments/a_2fcfd171ff8221236913b3e73a7422fdeb7e1015edcc9297f161b21a1dbced7b/CleanShot%202026-07-07%20at%2017.25.35@2x-20260707-142601.png?cb=a944869e1f9c6f9bb04dd01acd9eb464) Each top-level section contains settings related to a specific part of ActivityTimeline. For example, team-related settings are managed under **Teams** , user roles and capacity are managed under **Users** , and issue or event appearance settings are managed under **Issues** and **Events**. The **Configuration** tab contains the main application settings and is the recommended starting point when setting up ActivityTimeline for the first time. Inside the [**Configuration**](https://help.activitytimeline.com/at/configuration-settings.md) tab, you can use the left-side menu to access key setup areas. * [REST API Documentation](https://help.activitytimeline.com/at/rest-api.md) * [Main Configuration](https://help.activitytimeline.com/at/configuration-settings.md) * [Team Management](https://help.activitytimeline.com/at/team-management.md) * [Project Management](https://help.activitytimeline.com/at/project-management.md) * [User Management](https://help.activitytimeline.com/at/user-management.md) * [Issues and Events Configuration](https://help.activitytimeline.com/at/issues-and-events.md) * [Maintenance Page](https://help.activitytimeline.com/at/maintenance-page.md) * [Synchronization](https://help.activitytimeline.com/at/synchronization.md) * [Security Log](https://help.activitytimeline.com/at/security-log.md) * [Migration of ActivityTimeline from Jira Server/DC to Jira Cloud](https://help.activitytimeline.com/at/migration-of-activitytimeline-from-jira-server-dc-.md) * [ActivityTimeline Cloud vs. Server/Data Center Feature comparison](https://help.activitytimeline.com/at/activitytimeline-cloud-vs-server-data-center-featu.md) * [Integration with External Calendars](https://help.activitytimeline.com/at/integration-with-external-calendars.md) * [Standard vs Advanced Edition](https://help.activitytimeline.com/at/standard-vs-advanced-edition.md) --- language: "en" --- # Advanced Auto Issue Scheduling ActivityTimeline allows you to automatically schedule Jira issues on users' timelines based on their availability. The system can review **Jira issues that are already assigned to users but have not yet been scheduled in ActivityTimeline.** It then places these issues on the Planner according to each user's available capacity, existing workload, and non-working events such as vacations, days off, or holidays. This helps managers quickly create a realistic plan without manually dragging each issue to the timeline. ## Before You Start Auto Schedule works with Jira issues that are: * assigned to users from the currently selected team; * not yet scheduled on the timeline, unless you are rescheduling overdue issues; * estimated with a Remaining Estimate. Issues without a Remaining Estimate will not be scheduled automatically, because ActivityTimeline needs an estimate to calculate how much capacity is required. For better scheduling results, make sure that user availability, vacations, days off, issue priorities, and due dates are up to date. ## Run Auto Schedule To automatically schedule Jira issues: 1. Open the **Planner** module. 2. Select the required team. 3. Open the **Issue Panel**. 4. Click **Extra**. 5. Select **Auto Schedule**. ![CleanShot 2026-07-09 at 16.34.43@2x-20260709-133454.png](https://help.activitytimeline.com/__attachments/a_74bb64271574e92658659953f16beae4f894e321a7de014b69e525be533a2dae/CleanShot%202026-07-09%20at%2016.34.43@2x-20260709-133454.png?cb=cd02631d656c633bab0d2e3829c352e6) 6. Choose which issues should be included. | **Option** | **Description** | |----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Automatically schedule all issues assigned to the current team** | Schedules unscheduled issues assigned to users in the selected team. | | **Automatically schedule all issues assigned to the current team and displayed on the left panel** | Schedules only issues assigned to the current team that are currently visible in the Issue Panel. This is useful when filters are applied and you want to schedule only the filtered list of issues. | 7. Select additional scheduling options if needed. | **Option** | **Description** | |-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Use Placeholders** | Creates placeholders instead of scheduling actual Jira issues. This allows managers to review the proposed schedule before applying it to real Jira tasks. | | **Reschedule overdue tickets only** | Reschedules only overdue issues that were planned in the past but have not been completed. | | **Skip Existing Placeholders** | Skips issues that already have placeholders scheduled on the timeline. | | **Schedule Start Date** | Defines the date from which ActivityTimeline should start placing issues on the timeline. | 8. Set the **Schedule Start Date**. 9. Run the scheduler. ![CleanShot 2026-07-09 at 16.37.56@2x-20260709-133815.png](https://help.activitytimeline.com/__attachments/a_9dc4dc7a2788f378642eb99fa8aec06b53ec94c5880261b7b6764801b983c231/CleanShot%202026-07-09%20at%2016.37.56@2x-20260709-133815.png?cb=cd4de634602089840260b8d99c4e69f9) ActivityTimeline will review the selected issues and schedule them on the timelines of the assigned users. ## Using Placeholders for Auto Scheduling Enable **Use Placeholders** when you want to review the automatically generated schedule before scheduling real Jira issues. In this mode, ActivityTimeline creates placeholders for the selected issues. Managers can review the proposed plan and then approve the placeholders to replace them with actual Jira tasks. ![CleanShot 2026-07-09 at 16.41.59-20260709-134338.gif](https://help.activitytimeline.com/__attachments/a_59934d103343ca96a708624995eb4a992815d925b7a789c2a25235caa1bdcd9c/CleanShot%202026-07-09%20at%2016.41.59-20260709-134338.gif?cb=dcbd790ea6751f656116d2f75e2a0eb4) This is useful when you want to validate the schedule first, especially for larger teams or project plans. ## How ActivityTimeline Schedules Issues When Auto Schedule runs, ActivityTimeline checks the selected issues and places them on the assigned users' timelines based on available capacity. The system considers: * the issue assignee; * Remaining Estimate; * user availability; * existing scheduled work; * vacations, days off, and other non-working events; * issue priority and due dates, depending on configuration. The scheduler tries to place work on available days and avoid overload where possible. For example, if a user has vacation scheduled for two days, ActivityTimeline will avoid those days and place work on available working days instead. If one issue has a higher priority or earlier due date, it may be scheduled before lower-priority work. ## **Example** A user has two unscheduled Jira issues assigned: | **Issue** | **Remaining Estimate** | **Priority** | |-----------|------------------------|--------------| | Issue A | 8 hours | Major | | Issue B | 1 hour | Normal | ActivityTimeline reviews the user's availability, current workload, priorities, and due dates. ![5-20240916-105236.webp](https://help.activitytimeline.com/__attachments/a_ec9e3e06f22c287c162205b2df1b3ec0ea8f9c058f0efc1107d31dd075f3ac34/5-20240916-105236.webp?cb=97499bb8c3a4658cc0c742e766825cd1) The 8-hour issue is scheduled on a day with enough available capacity. The 1-hour issue is scheduled on another available slot if adding it to the same day would overload the user. ## Important Notes Auto Schedule works only with issues that have a **Remaining Estimate**. Issues without estimates are not scheduled automatically. The scheduling result may depend on issue priority, due dates, user availability, existing workload, and ActivityTimeline configuration. Please ensure that priorities are configured correctly under **Configurations → Issues → Issue Settings** for the Auto Scheduler to function as expected with priority-based settings --- language: "en" --- # Advanced Settings The **Advanced Settings** page allows ActivityTimeline administrators to configure system-level settings, synchronization limits, Jira permission handling, and custom functionality. To access this page, go to: **Configuration → Advanced Settings** These settings should be updated carefully, as they may affect issue visibility, synchronization performance, workload calculations, and overall application behavior. ## System Notification Message The **System Notification Message** field allows administrators to display a message to all users when they open ActivityTimeline. ![CleanShot 2026-07-08 at 12.21.45@2x-20260708-092148.png](https://help.activitytimeline.com/__attachments/a_cfb4d09d9363853c21eba9410ea61805a75964e5462ac710ae7d2ad84a2321be/CleanShot%202026-07-08%20at%2012.21.45@2x-20260708-092148.png?cb=46a312b4a4484aceb04683a7834e9675) For example, you can use this message to notify users that ActivityTimeline will be unavailable during a planned maintenance window. ## Reuse Jira Permissions per Project This setting defines whether ActivityTimeline should reuse Jira Project Permissions in addition to built-in ActivityTimeline user roles. ![CleanShot 2026-07-08 at 12.22.36@2x-20260708-092239.png](https://help.activitytimeline.com/__attachments/a_fded05282531d93ac04ae2ea8895cdf5d4b0d1018426abfb16c422aa54e0419a/CleanShot%202026-07-08%20at%2012.22.36@2x-20260708-092239.png?cb=9377c0a19316e9e9048d676a74fda4ee) When enabled, ActivityTimeline checks whether the logged-in user has access to a Jira project before displaying related issues and project data. Possible values: * **Checked** --- Jira Project Permissions and ActivityTimeline user roles are both used to filter visible issues, projects, and teams. * **Unchecked** --- only ActivityTimeline user roles are used to filter visible issues and teams. Default value: **Checked** This setting is recommended for most organizations because it helps keep ActivityTimeline visibility aligned with Jira project access. ## Reuse Jira Permissions per Issue This setting defines whether ActivityTimeline should reuse Jira issue-level permissions in addition to built-in ActivityTimeline user roles. ![CleanShot 2026-07-08 at 12.23.02@2x-20260708-092306.png](https://help.activitytimeline.com/__attachments/a_42b1d0193d37d4afde5588ca1f0865a87dc8ede5e21c652184c0032aecb203ad/CleanShot%202026-07-08%20at%2012.23.02@2x-20260708-092306.png?cb=073a5f29658a98e0cc37f24867a37efb) When enabled, ActivityTimeline checks Jira issue permissions for each logged-in user. Possible values: * **Checked** --- Jira Issue Permissions and ActivityTimeline user roles are both used to filter visible issues, projects, and teams. * **Unchecked** --- only ActivityTimeline user roles are used to filter visible issues and teams. Default value: **Unchecked** Enabling this setting may decrease dashboard performance because ActivityTimeline needs to perform additional permission checks. ## Decimal Delimiter Symbol This setting defines which decimal delimiter should be used for estimate and worklog hour values. ![CleanShot 2026-07-08 at 14.14.44@2x-20260708-111447.png](https://help.activitytimeline.com/__attachments/a_e537508d2749720410983db225e989b91a29746791034f3edbf5c099abe96b5e/CleanShot%202026-07-08%20at%2014.14.44@2x-20260708-111447.png?cb=4605e02ec792c5d672e72f5af7bdd78f) It is important to configure this correctly so Jira can properly read and process estimate and worklog values. Recommended values: * **Decimal Point** --- commonly used for English and Chinese locales. * **Decimal Comma** --- commonly used for German, Spanish, French, Italian, and similar locales. Default value: **Decimal Point** ## Allow Team Leads to Manage Users in Their Teams This setting defines whether users with the **Team Lead** or **Power Team Lead** role can add or remove users from the teams they manage. ![CleanShot 2026-07-08 at 14.15.10@2x-20260708-111513.png](https://help.activitytimeline.com/__attachments/a_8e0c80e2bf24f9c1d6e0baed646c4d177c9db030bd7f6b90cf214f0bcd050881/CleanShot%202026-07-08%20at%2014.15.10@2x-20260708-111513.png?cb=438a21e488283e6a9db3a2d2f43022a8) Possible values: * **Yes** --- Team Leads and Power Team Leads can add or remove users from their managed teams. * **No** --- Team Leads and Power Team Leads cannot manage team membership. Default value: **No** Use this setting carefully. If enabled, Team Leads may be able to add users to their teams and, as a result, gain visibility into those users' schedules and worklogs within the managed team context. ## Custom Functionality The **Custom Functionality** field is used to enable specific ActivityTimeline features that are not turned on by default. ![CleanShot 2026-07-08 at 14.15.43@2x-20260708-111546.png](https://help.activitytimeline.com/__attachments/a_80f4b899477b26445568a3a3d94760f3880d28c5a8979af29608b52c1a7d8fa6/CleanShot%202026-07-08%20at%2014.15.43@2x-20260708-111546.png?cb=0fa4dad2eb47906b00bc2ef390b72f16) These values are provided by the ActivityTimeline support team when needed for a specific use case. Multiple values can be separated by coma. Default value: **0** We do not recommend changing this field unless instructed by the ActivityTimeline support team. Incorrect values may affect application behavior. ## Number of Issues to Load from Jira This setting defines the maximum number of Jira issues ActivityTimeline should retrieve during Setup Wizard synchronization. ![CleanShot 2026-07-08 at 14.16.21@2x-20260708-111625.png](https://help.activitytimeline.com/__attachments/a_c9bdd03f15f1fbf9367bc8f7b048c89dfa333b303fe05459755a87ad86b9127a/CleanShot%202026-07-08%20at%2014.16.21@2x-20260708-111625.png?cb=145a331f92ddd2da910488d85c037ce1) Default value: **10,000** Recommended maximum: **100,000** If you have just started a trial and some Jira issues are missing in ActivityTimeline, you may need to increase this limit and run synchronization again. ## Maximum Issues for Budget Calculation This setting defines the maximum number of issues that can be included in a single Budget scope calculation in the Finances module. ![CleanShot 2026-07-08 at 14.16.37@2x-20260708-111643.png](https://help.activitytimeline.com/__attachments/a_b21d6f08b2f5196d79ad97f92c4d001549f2042558924be861530fc3b46c4eda/CleanShot%202026-07-08%20at%2014.16.37@2x-20260708-111643.png?cb=dfc6067bde75097d3191ce6d9751f1e9) If the limit is exceeded, calculation results may be truncated. Default value: **5,000** Recommended maximum: **10,000** ## Number of Worklogs to Load from Jira This setting defines the maximum number of worklogs ActivityTimeline should synchronize from Jira. ![CleanShot 2026-07-08 at 14.17.00@2x-20260708-111703.png](https://help.activitytimeline.com/__attachments/a_a7208d7518ba5a0ed54f4ffde63adcc20059569e9acc50b4c9275b58b21da4ca/CleanShot%202026-07-08%20at%2014.17.00@2x-20260708-111703.png?cb=f7f79afc04eed3f66245f6425a5542a6) Default value: **30,000** Recommended maximum: **100,000** If your organization has a large amount of historical worklog data, you may need to increase this value before running a full worklog synchronization. ## Maximum Number of Worklogs for Timesheet Report This setting defines the maximum number of worklogs ActivityTimeline retrieves from the database for a single Timesheet report in the Track view. ![CleanShot 2026-07-08 at 14.17.28@2x-20260708-111733.png](https://help.activitytimeline.com/__attachments/a_e0fdad16eabe0015509ee75f54db21eb8f45c6ff5001b4edad8219e624911ef9/CleanShot%202026-07-08%20at%2014.17.28@2x-20260708-111733.png?cb=b32814c7fa0eb237f01440d866ec7f16) Default value: **15,000** Maximum value: **50,000** If a Timesheet report contains more worklogs than the configured limit, the report may not include all matching records. ## Synchronize Issues and Worklogs Updated Within This Period This setting defines how far back ActivityTimeline should synchronize issues and worklogs based on their last modified date. ![CleanShot 2026-07-08 at 14.17.51@2x-20260708-111755.png](https://help.activitytimeline.com/__attachments/a_5d6d5360c095771e0830063024cfeba33a0291a932af6ad80c062f2501fa20bf/CleanShot%202026-07-08%20at%2014.17.51@2x-20260708-111755.png?cb=8bc255fca424a460be3d0d42539edd5a) Issues and worklogs that were last modified earlier than the configured period will not be synchronized. Default value: **12 months** This setting is useful for limiting synchronization scope and improving performance, especially in large Jira instances. If you need to import older historical data, increase this value before running synchronization. ## Amount of Issues to Load per Request This setting defines how many issues ActivityTimeline should load in each request to the server during synchronization. ![CleanShot 2026-07-08 at 14.18.12@2x-20260708-111816.png](https://help.activitytimeline.com/__attachments/a_1ab383c59abed0bbd68ac5e7443c90488c1c94d590ab50650a2c36f861455e0b/CleanShot%202026-07-08%20at%2014.18.12@2x-20260708-111816.png?cb=40e5be1f3a0ff07acea15b8ecea85b5f) Default value: **1,000** In most cases, this value should not be changed unless recommended by the ActivityTimeline support team. ## **Issue ID in Jira** This is a system property used by ActivityTimeline. ![CleanShot 2026-07-08 at 14.18.32@2x-20260708-111837.png](https://help.activitytimeline.com/__attachments/a_6b7dc3d9aaca936d3905897abd0a544a710e1d158faab7184c924442d2c1c1af/CleanShot%202026-07-08%20at%2014.18.32@2x-20260708-111837.png?cb=1b480c81bba092a2c1d77d9215ffb03e) Default value: **10011** or the value detected for your Jira instance. This setting should not be changed manually. ## **Unresolved Resolution ID** This setting defines an additional Jira resolution status ID that should be treated as unresolved by ActivityTimeline. ![CleanShot 2026-07-08 at 14.18.49@2x-20260708-111853.png](https://help.activitytimeline.com/__attachments/a_2a054fafcdc38b8eaa9b349d74116364aa76ba46636d3a160682407a8422534e/CleanShot%202026-07-08%20at%2014.18.49@2x-20260708-111853.png?cb=6ed1023ec95aec90ff6e1f06c52b3ba1) Jira issues with this resolution ID will appear in the left Issue Panel in addition to all unresolved issues. Default value: **Empty** Use this setting only if your Jira workflow has a specific resolution configuration that requires additional handling in ActivityTimeline. ## Important Notes Advanced Settings can affect synchronization, issue visibility, reporting limits, permission behavior, and performance. Before changing synchronization limits, Jira permission settings, or custom functionality values, we recommend contacting the ActivityTimeline support team. If you have just started a trial and cannot find some issues in ActivityTimeline, review the following settings first: * **Number of Issues to Load from Jira** * **Number of Worklogs to Load from Jira** * **Synchronize Issues and Worklogs Updated Within This Period** * Project activation under **Configuration → Projects** * Jira permissions for the affected projects For more details, please refer to the related documentation page: [Customer Q \& A - PLAN. Issue Panel \& Filters](https://help.activitytimeline.com/at/customer-q-a-plan-issue-panel-filters.md#I-started-a-trial-and-cannot-find-some-issues-in-ActivityTimeline) --- language: "en" --- # Timeline Aggregation Aggregation functionality is available starting from ActivityTimeline v9.4.0+ Timeline Aggregation provides a summarized view of scheduled work by grouping timeline items based on a shared Jira attribute. Instead of displaying every individual issue, ActivityTimeline combines related items into a single visual block, making it easier to analyze workloads and identify planning trends. Aggregation is particularly useful when reviewing resource allocation across teams or projects, as it helps you focus on the overall picture without being distracted by individual tasks. By default, Aggregation is disabled. To enable it, click the **Aggregation** icon on the right-side toolbar. ![CleanShot 2026-07-14 at 16.23.06@2x-20260714-132326.png](https://help.activitytimeline.com/__attachments/a_617f4649eda0f373021c25640a68eb1008ea79ce8c76278796bc5e049b4fe9b1/CleanShot%202026-07-14%20at%2016.23.06@2x-20260714-132326.png?cb=e5481920fb5726e67467ba252b671b7f) ## Available Aggregation Modes ActivityTimeline supports the following aggregation types: * Project * Epic * Issue Status * Issue Type * Issue Priority Simply select the desired aggregation mode to regroup the timeline. ![CleanShot 2026-07-14 at 16.31.11@2x-20260714-133119.png](https://help.activitytimeline.com/__attachments/a_0decdd0844948b35cf1933f6817ea9b168879013c685f08f6628174d5d7c0446/CleanShot%202026-07-14%20at%2016.31.11@2x-20260714-133119.png?cb=18cbfde91d6a8b7331d9f46e7cde726e) ### Aggregate by Project The **Project** view groups all scheduled work by Jira project. Instead of displaying individual issues, the Timeline shows one block for each project, allowing you to quickly understand: * which projects each user is working on, * the distribution of work across multiple projects. ![CleanShot 2026-07-14 at 16.29.38@2x-20260714-132942.png](https://help.activitytimeline.com/__attachments/a_26f6d16d762a391a07b5fda71eb925e4eee08cc30c3c75665e9ee5c35f804247/CleanShot%202026-07-14%20at%2016.29.38@2x-20260714-132942.png?cb=78c8ab9c27a0c18dc8d2ea005a02b15e) Each project is displayed using a different color for easier visual identification. ### Aggregate by Epic The **Epic** view groups issues according to the Epic they belong to. This helps managers understand: * which initiatives users are contributing to, * the overall progress of larger bodies of work. ![CleanShot 2026-07-14 at 16.29.56@2x-20260714-133001.png](https://help.activitytimeline.com/__attachments/a_1edfa318d390ab417a02f6e693db24aac4d989e8da19786cf22554caa1840133/CleanShot%202026-07-14%20at%2016.29.56@2x-20260714-133001.png?cb=ab590128b0aed315d5a3bbbb42aaf235) Each Epic is assigned its own color, making different initiatives easy to distinguish. ### Aggregate by Issue Status The **Issue Status** view groups work based on the current Jira workflow status. This provides a quick overview of how work is progressing and makes it easy to identify: * work currently in progress, * completed work, * planned work. ![CleanShot 2026-07-14 at 16.30.14@2x-20260714-133019.png](https://help.activitytimeline.com/__attachments/a_1dc8a175a5ccb566927febd6e5766c37e51e83869d0eae18da8c172ec5ce99de/CleanShot%202026-07-14%20at%2016.30.14@2x-20260714-133019.png?cb=d8176ae08750b586f1ec750788667377) This view is especially useful for monitoring workflow health and identifying bottlenecks. ### Aggregate by Issue Type The **Issue Type** view groups work according to the Jira issue type. ![CleanShot 2026-07-14 at 16.30.30@2x-20260714-133036.png](https://help.activitytimeline.com/__attachments/a_bf7f59f7c4e0ee9269bffb74ac33dc7077a66b4ebc54e47abd7f25bc912a23de/CleanShot%202026-07-14%20at%2016.30.30@2x-20260714-133036.png?cb=388a4c79f7807a192e01e069ac6da8fd) This helps teams understand the composition of their work and identify how effort is distributed across different types of activities. ### Aggregate by Issue Priority The **Issue Priority** view groups work according to the Jira priority assigned to each issue. This makes it easy to identify: * how much high-priority work is planned, * whether urgent issues are receiving appropriate attention, * the overall balance between critical and lower-priority tasks. ![CleanShot 2026-07-14 at 16.30.45@2x-20260714-133051.png](https://help.activitytimeline.com/__attachments/a_5fe3e7eea9a2c817fdd67936b134e35fe0f708a386c4f332075b6807d8a3800b/CleanShot%202026-07-14%20at%2016.30.45@2x-20260714-133051.png?cb=2e954e67fb28cc99c56d99510a2e0d2f) This view is particularly useful when reviewing team workload and ensuring that the most important work is scheduled appropriately. --- language: "en" --- # Alignment Timesheets This view is part of the[Advanced Edition](https://help.activitytimeline.com/at/standard-vs-advanced-edition.md) of ActivityTimeline Cloud. ## Overview The **Alignment report** in Timesheets allows you to compare **Planned time vs Logged time** over a selected period. ![image-20260508-144331.png](https://help.activitytimeline.com/__attachments/a_22472c5b0b529ecdc1f46ebaba5a07fda17bda2eddd2b98e0996f24f80e04f22/image-20260508-144331.png?cb=cd666062717f9d4d77245f54c6d49f6e) This report helps you understand how accurately the work was executed against the plan by showing: * How much time was **planned** * How much time was **actually logged** * the **difference (Δ Delta, Hours)** * the **ratio between them (Plan Match, %)** It is useful for managers, team leads, and project managers who want to track whether work is being logged according to expectations. ## Templates The report follows the same template structure as [Timeline Timesheets](https://help.activitytimeline.com/at/timeline-timesheet-track.md). ![CleanShot 2026-07-03 at 21.07.00@2x-20260703-180704.png](https://help.activitytimeline.com/__attachments/a_b658d1724fef482cdb55f023bf3cf8b37be621f5ad9d4c7c7e22d68e587da64f/CleanShot%202026-07-03%20at%2021.07.00@2x-20260703-180704.png?cb=be5a0f0bbf4439d22279611c9c1a5d7a) **User Timesheets** * Summary * By Project * By Issue * By Epic **Project Timesheets** * Summary * By User * By Issue * By Epic **Epic Timesheets** * Summary * By User * By Issue By default, the report opens in: **User Timesheets → Summary** ## How the Report Works The report compares **Planned time** and **Logged time** for each row and selected period. ![CleanShot 2026-07-03 at 21.06.05@2x-20260703-180631.png](https://help.activitytimeline.com/__attachments/a_eb873d60b1b499c010363b6a10f725ff6a83d00f2107763e3a09701a894bca59/CleanShot%202026-07-03%20at%2021.06.05@2x-20260703-180631.png?cb=21041c32000e7abae0a6c96e04adfff5) ### Planned Time Planned time is calculated from: * Jira issue **Original Estimate** * **Bookings** * **Placeholders** * [**Imported Calendar Events**](https://help.activitytimeline.com/at/integration-with-external-calendars.md) The calculation follows the same logic used in Planner. ### Logged Time Logged time is calculated from Jira worklogs. Optionally: * **Bookings** or **Calendar events** can be treated as logged time if this setting is enabled: **ActivityTimeline Configuration-\> Timesheets Configuration.** ![CleanShot 2026-07-03 at 21.07.31@2x-20260703-180738.png](https://help.activitytimeline.com/__attachments/a_ed6c06d5198ebf74e8cb734db58a0f09b0b2dc0c269d55e0fb3568940b2aaf44/CleanShot%202026-07-03%20at%2021.07.31@2x-20260703-180738.png?cb=2b04cc48c52fd730a31353aef88d4419) ## Key Metrics ### Δ Delta, Hours **Delta** shows the difference between logged and planned time. ![image-20260508-150804.png](https://help.activitytimeline.com/__attachments/a_eac525cce697c7fdebd871e45e457554eeb0f3d48521d15bf47e7c644dd5c06a/image-20260508-150804.png?cb=128034520206c5d5bd97ba753f27edae) Mouse over to see the details **Formula:** Δ = Logged time - Planned time Examples: * Planned 40h, Logged 45h → **+5h** * Planned 40h, Logged 38h → **-2h** * Planned 40h, Logged 40h → **0h** Interpretation: * **Positive (+)** → More time logged than planned * **Negative (-)** → Less time logged than planned ### Plan Match, % **Plan Match** shows the ratio between logged time and planned time. ![image-20260508-150855.png](https://help.activitytimeline.com/__attachments/a_71f4b8ef5bb4d58cff273d5b913e9c2a8088dc06a86d950d5ff3bbf639862358/image-20260508-150855.png?cb=eca4ac897528d389d0459de36f6ae68b) **Formula:** Plan Match (%) = (Logged time / Planned time) × 100 Examples: * Planned 40h, Logged 40h → **100%** * Planned 40h, Logged 20h → **50%** * Planned 40h, Logged 80h → **200%** Interpretation: * **100%:** Logged time exactly matches planned time. * **Above 100%:** More time was logged than planned. * **Below 100%:** Less time was logged than planned. Plan Match is a comparison ratio, not a performance score. ## Display Modes The report provides two display modes. ![CleanShot 2026-07-03 at 20.58.24@2x-20260703-175841.png](https://help.activitytimeline.com/__attachments/a_c637810bcb2fc0866c5c81773078b33a7613cde76a878b8bcaab37072b7a4f4e/CleanShot%202026-07-03%20at%2020.58.24@2x-20260703-175841.png?cb=d7448837038fd667768b42af82be2808) **1. Δ Delta, Hours (default)** * Time buckets display the difference between planned and logged time in hours, for example: * `+5h` * `-2h` * `0h` **2. Plan Match, %** * Time buckets show **percentage values** * Cells may include a progress-style fill ## Color Coding Cells are colored based on **Plan Match (%)**, regardless of the selected display mode. The current ranges are: * **Below 50%** → Yellow * **50%--86%** → Light green * **87%--101%** → Green * **101%--125%** → Light red / orange * **Above 125%** → Red ![CleanShot 2026-07-03 at 20.59.11@2x-20260703-175929.png](https://help.activitytimeline.com/__attachments/a_09b9aaf9e8f82555cdc3cd3fab8250e26158c36539cdb0d224bdfadc2046a8cd/CleanShot%202026-07-03%20at%2020.59.11@2x-20260703-175929.png?cb=8c9dbf0ba44142d4ac900d8cd9a70e1a) Color coding helps you quickly identify significant differences between planned and logged time. ## How Non-Working Time Affects the Report The Alignment Report compares **Planned time** with **Logged time**. It does not automatically adjust the comparison based on: * Days off. * Holidays. * Weekends. For example: * Planned: 40h * Logged: 24h Result: * **Plan Match:** 60% * **Delta:** -16h If the user also had two days off during the period, those days do not automatically reduce the planned value used in this comparison. **Important Behavior: When the User Has No Capacity for the Entire Period** If a user has no capacity for the entire selected time bucket, for example because of a full day or full week off, planned time is treated as **0h** for that period. ![CleanShot 2026-07-03 at 21.00.00@2x-20260703-180009.png](https://help.activitytimeline.com/__attachments/a_0b3caf29433919b6ac4ea1ce980869b6376b9b4793828228fa29c9fe50af0ad9/CleanShot%202026-07-03%20at%2021.00.00@2x-20260703-180009.png?cb=66d546ad968da746b762841248dd7c37) If time is still logged: * Planned: 0h * Logged: 8.5h * Delta: +8.5h * Plan Match: Not applicable ![image-20260508-152142.png](https://help.activitytimeline.com/__attachments/a_bd935226881ce268b3186fe214f838d0b27aa8fe1aca5aef4c28e007e99a89cf/image-20260508-152142.png?cb=37808cdf3e808f8c55ddedac49cd003a) The logged time is therefore shown as time recorded without corresponding planned time. ## Export to Excel You can export the Alignment Report using the **Excel** button. ![CleanShot 2026-07-03 at 21.00.47@2x-20260703-180103.png](https://help.activitytimeline.com/__attachments/a_93aaed5f697a628d0365e8b818a87b5c368e25efc63299d8d73d03deac866709/CleanShot%202026-07-03%20at%2021.00.47@2x-20260703-180103.png?cb=4603ff40ba3ad0345451f8f4ecd0d594) The export reflects the current report configuration, including: * Selected template. * Filters. * Grouping. * Time range. ## FAQ ### Why is Plan Match 200%? Because more time was logged than planned. Example: Planned 40h, Logged 80h → **200%** (2× the planned effort). ### Why is my Delta negative? Because logged time is lower than planned time. Example: Planned 40h, Logged 30h → **Δ = -10h**. ### Does the Alignment Report account for holidays, days off, or weekends? Not directly. The report compares Planned time with Logged time and does not automatically reduce planned time because of non-working days within the period. If a user has no capacity for the entire period, planned time is treated as 0h. ### Why is the cell colored when I am viewing Delta? Cell colors are always based on Plan Match (%), even when the report displays Delta values. ### Are Plan Match percentages averaged across rows? No. ActivityTimeline: 1. Sums Planned time. 2. Sums Logged time. 3. Calculates Plan Match based on those totals. This avoids misleading averages across rows. --- language: "en" --- # Applying Filters - Issue Panel You can filter issues on the issue panel in the Planner module by different criteria. ## Quick Filters Quick Filters provide the possibility to select multiple items in a dropdown list. If no specific items are chosen in the multi-select drop-down filter, all issues that belong to this filter will be displayed. ![CleanShot 2024-08-19 at 22.12.38@2x-20240819-191244.png](https://help.activitytimeline.com/__attachments/a_e11cc81a6025b077e0ea8762c863f67667c082e018016ccd094291fc99690795/CleanShot%202024-08-19%20at%2022.12.38@2x-20240819-191244.png?cb=bb8d10885ae1a1e4a39b284fa3be5665) If no filters are applied or only the Resolution filter, issues that were updated within the last 30 days will be displayed. **Hierarchy of filtered issues** If an issue (epic, story, task, etc.) has related issues or sub-tasks, they will be displayed with the "+/-" icon. Issues will be loaded on-demand only when a hierarchy level is expanded, or they will be hidden when a hierarchy level is collapsed. ### Filter by Assignee In case a user wants to only seethe issues assigned to a specific team or team member, he/she should select the required assignee from the **Filters → Assignee** multi-select drop-down list. The available options are: * Me - All (links) * All * by Team * by People * Unassigned ![CleanShot 2025-05-30 at 18.01.16@2x-20250530-150119.png](https://help.activitytimeline.com/__attachments/a_6694a890ba0e272d72f5d0f190033500870e61dc9c49533413b72b2397a8d93c/CleanShot%202025-05-30%20at%2018.01.16@2x-20250530-150119.png?cb=c2dcace5ace2436b15cb938f1d235396) Once the filter option is set, the system will show only the set of JIRA tickets that are assigned to a particular team. #### Filter by Schedule To filter by schedule, select the required filter option from the **Filters** *→* **Schedule** multi-select drop-down list. The available options are: * Scheduled Tickets * Non-Scheduled Tickets * Due Soon Tickets * Overdue Tickets. E.g., if Scheduled Tickets are selected, the system will show only the tickets that are already planned or scheduled. You can assign a work item (JIRA ticket) to a person and then apply the filter at **Filters** *→* **Schedule** *.*Now you should see the newly assigned work item. If the person with a newly assigned ticket belongs to multiple teams, and if you apply another Filter by Assignee option (e.g., Development Team), along with Filter by Schedule, then you'll see that the newly assigned work of that person is there as well. You can combine multiple different filters. For example, select Team from **Filters → Assignee** drop-down, and **Non-Scheduled Tickets** from **Filters → Schedule drop-down**. The user should see all the issues including JIRA tickets that are not yet scheduled to the development team. ![CleanShot 2025-05-30 at 18.00.20@2x-20250530-150024.png](https://help.activitytimeline.com/__attachments/a_56c4eac79c49f38638f637ff57313069d6da216b01bf47aa617c796c735642cd/CleanShot%202025-05-30%20at%2018.00.20@2x-20250530-150024.png?cb=2975ff3e3d4207c9fb81e42a98ea5224) You can also**Filter by Due Soon Tickets** which corresponds to all JIRA tickets that have a due date within the next five days, or **Overdue Tickets** which missed the due date or were scheduled in the past and are not resolved yet. ![CleanShot 2025-05-30 at 18.00.49@2x-20250530-150053.png](https://help.activitytimeline.com/__attachments/a_8b9d98d10777b95278ed80c1e089865b5a310aa2316c7a1c608b2ea642e6370a/CleanShot%202025-05-30%20at%2018.00.49@2x-20250530-150053.png?cb=67aaae11af665e5be1efaab14f5e4ca2) Three main categories of tickets are considered overdue: 1. Tickets that have Due Date missed; 2. Tickets that are open and not resolved yet, but that were scheduled in the past (last week/month/year etc.); 3. Tickets that were scheduled after the due date #### Filter by Project To filter by project, select the required project from the **Filters** *→* **Project** drop-down list. #### Filter by Resolution To filter tickets based on resolution, select the required resolution to filter from the **Filters** *→* **Resolution** multi-select drop-down list. The system will collect all the possible resolution options available in JIRA system. You will also get custom resolutions that will appear based on JIRA tickets. #### Filter by Status To filter by status, select the status from the **Filters** *→* **Status** drop-down list. #### Filter by Type To filter by the issue type, select the type of the issue from the**Filters** *→* **Type** drop-down list. ![CleanShot 2025-05-30 at 17.59.39@2x-20250530-145944.png](https://help.activitytimeline.com/__attachments/a_9af5430841c373bf9692b2767a49f1900bbb3204c279a5e0b13e1054328dd8ec/CleanShot%202025-05-30%20at%2017.59.39@2x-20250530-145944.png?cb=d94f0e2bfd6306da8c5d689d9c7dca1a) Days off, vacations, and sick leaves will always appear on the timeline, regardless of any filters applied. ## Agile Filters ### Filter by Board and Filter by Sprint If a customer uses JIRA software, there is a possibility to filter by**JIRA** **Agile Board and Sprint** ***.*** In the **Filters** tab **→** **Agile Filters** section, select the board and sprint options from the respective drop-down lists. ![image-20230127-144515.png](https://help.activitytimeline.com/__attachments/a_74d50bf26780fe713e8cd8bd12fb34c58f5e08190dc2129507e3224d53a94137/image-20230127-144515.png?cb=b54d9fd78d22bc5854161f33023c7c4e) ## Jira Filters If a user has any filters saved in Jira, he/she can filter the issues in ActivityTimeline by selecting the corresponding filter. Filters are dependent on who is currently logged into the system. So different users might see different filters. ## Applying Filters to Timelines One can apply filters from the left Issues panel **→** Filters to the right Timeline panel. To have a timeline apply to all the set filters, a user has to: 1. Go to Filters in the left panel 2. Select filtering criteria 3. Switch on **Apply Filters to Timelines** option. ![image-20230127-144724.png](https://help.activitytimeline.com/__attachments/a_680520fc0554b955129b3f781052c7f6fbe6095b8336ef471dbf79eaddb5b7f2/image-20230127-144724.png?cb=e66ba3188c70e3af7e907e0ebedd1f7f) The system will apply filters to the timelines in the dashboard. If a user switches off the option *Apply Filters to Timelines,*all tickets and events are returned and are visible on the timelines. [7.mp4](https://help.activitytimeline.com/__attachments/a_eb0bf633f994992a9b21bf27fbda97fef346ba13d4fdadd939074a406de04448/7.mp4.md?cb=b121cea4596c6e2aae93627d082aa89d) ## Show Custom Events Filtering works by displaying only issues or events that fully meet the specified criteria. Bookings, placeholders, and notes will be visible only when the appropriate **'Type'** , **'Assignee'** , or **'Project'** filter is applied. They will not appear if filters specific to Jira tasks, such as **'Resolution'** or **'Version'**, are applied. To display custom events even if they do not match some of the Jira-specific criteria, enable the **'Show Custom Events'** toggle. This toggle becomes available after clicking on **'Apply Filters to Timeline'**. ![CleanShot 2024-12-23 at 14.25.46@2x-20241223-122636.png](https://help.activitytimeline.com/__attachments/a_a6420fb7982c791d0d0673cda8c1e334371f111d1b89b7cc789a0b5bab80ed87/CleanShot%202024-12-23%20at%2014.25.46@2x-20241223-122636.png?cb=60a76f640e72c51b104d787daa5d618b) --- language: "en" --- # Schedule Jira Issues and Custom Events When you have your teams created, and users assigned to the required roles and positions, you are ready to start planning actual Jira tasks. ## Assign Jira Tasks The whole concept behind scheduling tasks in ActivityTimeline is fairly straightforward, you just take the task from Issue Panel and drag'n'drop it to the user's timeline, where you can then re-size it or even split it between users or dates. ![Assign Jira Tasks activity.png](https://help.activitytimeline.com/__attachments/a_ffb815413ccdc1a632fdde7a6e1c2d86561fb3c201438625ec3b5d023477a01f/Assign%20Jira%20Tasks%20activity.png?cb=3395ed3f56c00a382a39da2e4f734668) If you followed our advice in the previous section of this guide, you also have the option to assign tasks not only via drag'n'drop, but by going to your Jira and specifying **Start/End dates** there: [Assign Jira Tasks ActivityTimeline.mp4](https://help.activitytimeline.com/__attachments/a_a47892e0fa0d0cfafd3f7376a41e719177992e734e77cb891b2e42c54bf853c1/Assign%2520Jira%2520Tasks%2520ActivityTimeline.mp4.md?cb=223447501b41cbd29fe457e071d16b61) For people who use Scrum a lot and are not really interested in scheduling individual tasks, the system will read **Start/End dates of the sprint**and schedule tasks assigned to a user based on these days: ![CleanShot 2025-05-29 at 17.39.33@2x-20250529-144014.png](https://help.activitytimeline.com/__attachments/a_d129b94656a4dcc7623202c9298b8596cae6f1b587ed67271667b7fb511d91b2/CleanShot%202025-05-29%20at%2017.39.33@2x-20250529-144014.png?cb=d02a834d3f2a0b2603f19372cece2d6c) ## Custom Events As for **local events,** you can create them simply by selecting a specific period on the calendar and choosing which event to create. You can check the details about Custom Events [here](https://help.activitytimeline.com/at/basic-concepts-jira-tasks-local-events.md). [Assign Jira Tasks ActivityTimeline 2.mp4](https://help.activitytimeline.com/__attachments/a_e4e5026f356842029ab90fded5ee28d7a93e616ebf7a9f93d961ab13337fdfc6/Assign%2520Jira%2520Tasks%2520ActivityTimeline%25202.mp4.md?cb=370aa60f60e18663824bd086bf883d78) When you unschedule a local event from the user, it disappears, as there is no backlog for events at the moment. ## What Happens Next Once you are all set, go to the next step, which is exploring [Workload Calculation Modes](https://help.activitytimeline.com/at/workload-calculation-algorithm.md) options. --- language: "en" --- # Configure Users, Roles, and Capacity Resources are central to ActivityTimeline. To plan work effectively, we recommend configuring your users before you start scheduling tasks. The most important user settings are: * **Roles** -- define what users can access and manage. * **Capacity \& Workload Schemes** -- defines each user's working capacity. * **Positions \& Skills** -- add additional information for planning, searching, reporting, and Functional Teams. ## Roles In ActivityTimeline, **roles define user permissions**. They control what each person can access and manage in the application. For full details, see: [User Roles and Permissions](https://help.activitytimeline.com/at/user-roles-and-permissions.md) As a general recommendation, you can use the following setup: * **Administrator** --- for Jira admins or users responsible for ActivityTimeline configuration. This role can also be assigned to users who are not Jira administrators. * **Manager** --- for users who plan and manage work for others, such as Project Managers, Business Analysts, Team Leads, and resource managers. * **Employee** --- for users who only need to manage their own tasks, schedule, and worklogs. ![CleanShot 2025-09-30 at 15.49.51@2x-20250930-124956.png](https://help.activitytimeline.com/__attachments/a_70aa3ee4dc269e2cc0551e5a0b2f482351ceb6a2b30d50c16473326fabaa39e3/CleanShot%202025-09-30%20at%2015.49.51@2x-20250930-124956.png?cb=422c71cfda63fc4785b830e670852072) To save time, go to **Configuration → Users → Bulk Mode** to assign roles to multiple users at once. Bulk Mode can also be used for positions and skills. ![2-20240911-072957.webp](https://help.activitytimeline.com/__attachments/a_b3f862072693c43448fd6203c5d4e1d03650bb7fbdfc0f89141ec0510c967062/2-20240911-072957.webp?cb=c14a74b3c138efb9e461119ed93513a2) ## Capacity and Workload Schemes After assigning user roles, the next important step is to configure user capacity. Capacity affects workload indicators, availability, utilization, and forecasting. In ActivityTimeline, capacity can be managed in two related ways: * [Personal Capacity / Involvement](https://help.activitytimeline.com/at/personal-capacity-involvement-management.md) --- defines how much time a resource is available for a specific day. * [Workload Schemes](https://help.activitytimeline.com/at/workload-schemes.md) --- define a reusable working schedule, including working days and available hours, that can be assigned to users or groups. ## Positions \& Skills Positions and Skills add useful context to user profiles. After creating your teams and assigning user roles, we recommend adding each user's position and skills. You can create new positions or skills directly by typing them into the corresponding field in the user profile. ![CleanShot 2025-09-30 at 15.53.08@2x-20250930-125347.png](https://help.activitytimeline.com/__attachments/a_21db6055a1446bb3bf810ca0b2bf7af0b2850f4ac8f3a619ed4031df27a42198/CleanShot%202025-09-30%20at%2015.53.08@2x-20250930-125347.png?cb=5453b0a7d8eb0958ed3297afcc2703c2) ### What can you do with Positions \& Skills? * Use positions and skills to find people with a specific skill set or role. For example, you can search for users who have a certain skill when you need the right person for a task or project. ![CleanShot 2025-09-30 at 15.54.36@2x-20250930-125441.png](https://help.activitytimeline.com/__attachments/a_4d4758665002383b592877465a43a57fdf7ba245edff201cb39cb20091a3f4cd/CleanShot%202025-09-30%20at%2015.54.36@2x-20250930-125441.png?cb=6ed946a347c6ea44cdb2289424f34358) * **Functional Team**can be generated based on skills or position. This means ActivityTimeline can automatically add users to a team when they match the required criteria. For more details, see: [Functional Team Administration](https://help.activitytimeline.com/at/functional-dynamic-team-administration.md) ![CleanShot 2025-09-30 at 15.55.16@2x-20250930-125520.png](https://help.activitytimeline.com/__attachments/a_916d85cd6d515917b5c1062e5a6c0dac4b3c9bf8ba8166d7c08d35650d8e8ecd/CleanShot%202025-09-30%20at%2015.55.16@2x-20250930-125520.png?cb=a74a0406ead8994016cfbf0e13b3f16b) * **Reports** can be generated based on positions or skills to help you understand when people with specific expertise are available. This is useful when planning work that requires particular roles, qualifications, or technical skills. ![CleanShot 2025-09-30 at 15.56.49@2x-20250930-125657.png](https://help.activitytimeline.com/__attachments/a_4dc1214a2fb06ca06e5f9f3efc34c13adddea25e1af076d6d7983693f3c698d2/CleanShot%202025-09-30%20at%2015.56.49@2x-20250930-125657.png?cb=2a447c46604f430478ee2fc8d808e3af) * You can also use Skills as**location tags.**For example, if your team is geographically distributed, you can add locations such as US, EU as tags. ![CleanShot 2025-09-30 at 15.59.38@2x-20250930-125943.png](https://help.activitytimeline.com/__attachments/a_21e5ccf9306852e4ad236a3d7859830f5482eacf99c61b2c5dd89ee81eae424f/CleanShot%202025-09-30%20at%2015.59.38@2x-20250930-125943.png?cb=239c7fbdf6c8c1bc08e05485ca211cac) You can then create 'location-based' teams by using **'Functional Team'** feature: ![CleanShot 2025-09-30 at 16.00.16@2x-20250930-130019.png](https://help.activitytimeline.com/__attachments/a_920b93969ad267f53af3b8b24b3f8e5de70237b5d2f141b49bd6c0b20cf43295/CleanShot%202025-09-30%20at%2016.00.16@2x-20250930-130019.png?cb=f64339700ca77a3ec13c65b787fc2b29) System added everyone with 'US' location tag to the US team: ![CleanShot 2025-09-30 at 16.01.51@2x-20250930-130204.png](https://help.activitytimeline.com/__attachments/a_db796bc0c3757481f1081ffbfd15fd7299df88252bb1b3a1f8c88d09cafb4780/CleanShot%202025-09-30%20at%2016.01.51@2x-20250930-130204.png?cb=1507dd20086dbf16e23ab085f9357eae) ## Manage Users in Bulk If you're configuring a large number of users, ActivityTimeline provides several ways to simplify administration. Using **Configuration → Users → Bulk Mode**, you can update: * roles, * positions, * skills, * and other user properties for multiple users simultaneously. If your organization already manages users through Jira groups, you can also use [**Group Mapping**](https://help.activitytimeline.com/at/jira-groups-management-in-activitytimeline.md) to automatically assign users skills, positions and etc. ## What Happens Next Once user roles, positions, and skills are configured, you can continue to the next setup step: [Map Custom Fields](https://help.activitytimeline.com/at/map-custom-fields.md) --- language: "en" --- # AT REST API ActivityTimeline has its own API, it is switched off by default and can be turned on manually by ActivityTimeline Admin in **ActivityTimeline Configuration-\>REST API**: ![1-20240919-085124.png](https://help.activitytimeline.com/__attachments/a_37190d235e039ebc3cc357db3f304202f42384e4561ee12d2a3fcef026180daf/1-20240919-085124.png?cb=ff6743f7b5addfb52afaa24eb23b0d45) It is possible to export list of all teams and users, their timeline schedules and list of custom events. You can also create custom events on users' timeline using REST API (like bookings, holidays, vacations, etc). The detailed documentation is available via the link below: [REST API](https://help.activitytimeline.com/at/rest-api.md) --- language: "en" --- # Displaying Issues Based on Sprint Dates For teams that work with Jira sprints, ActivityTimeline can display assigned sprint issues on user timelines using the sprint start and end dates. This is the default behavior when: * The issue belongs to an active or planned Jira sprint. * The sprint has defined **Start** and **End** dates. * The issue is assigned to a user. * The issue does not already have mapped start and end dates that take priority over sprint dates. This allows users' timelines to be populated automatically without manually scheduling each sprint issue on the Planner. ![1-20240919-082353.webp](https://help.activitytimeline.com/__attachments/a_2b12c96eb0749f1387cde95740f232af2930888d43119a26beee0dd129fdd3f9/1-20240919-082353.webp?cb=14bfccf1e9da7146ef9a7b8daac76371) ## How It Works When this option is enabled (*default*), ActivityTimeline can use the start and end dates of the Jira sprint as the planned dates for the issues included in that sprint. This is useful when: * Your team plans work in Jira sprints. * Sprint dates are already defined in Jira. * Issues are assigned to users. * You want sprint issues to appear automatically on users' timelines in ActivityTimeline. ### Date Field Priority By default, ActivityTimeline gives higher priority to mapped **Issue Start Date** and **Issue End Date** fields than to sprint dates. This means that if an issue already has mapped start and end dates in Jira, ActivityTimeline will use those dates instead of the sprint dates. To display issues based on sprint dates, make sure that: * The mapped Issue Start/End Date fields are empty in Jira, or * Start/End Date fields are not mapped in ActivityTimeline. ### Prioritizing Sprint Dates If you want ActivityTimeline to always display issues based on sprint dates when a sprint is selected, you can enable the custom functionality. To enable it, go to: **Configuration → Advanced Settings → Custom Functionality** Paste the following value: **PRIORITIZE_SPRINT_DATES** Then click **Update**. When **PRIORITIZE_SPRINT_DATES** is enabled, manually dragging and dropping tasks on the Planner may behave differently. For example, if you drag a task from the Issue Panel to a user or move it from one user to another, the task will initially appear on the dates where you dropped it. However, after refreshing the Planner, the task will be displayed according to the sprint start and end dates. ![CleanShot 2024-09-06 at 17.50.10-20240906-145306.gif](https://help.activitytimeline.com/__attachments/a_6627c7e7480cf05057f45cf383e7224d6ebe0930651030d46b3e3eff30d5ec40/CleanShot%202024-09-06%20at%2017.50.10-20240906-145306.gif) --- language: "en" --- # Basic Concepts This page introduces four ideas you'll see throughout ActivityTimeline: * [Resources \& Teams](https://help.activitytimeline.com/at/basic-concepts-resources-teams.md) --- the people (and how they're grouped) whose time and availability ActivityTimeline tracks. * [Personal \& Team Timelines](https://help.activitytimeline.com/at/basic-concepts-personal-team-timelines.md)--- the calendar views where work gets scheduled: for one person in **Workspace** , for a whole team in **Planner**. * [Jira Tasks \& Custom Events](https://help.activitytimeline.com/at/basic-concepts-jira-tasks-local-events.md) --- Jira issues appear automatically; Custom Events (vacation, bookings, notes) are added directly in ActivityTimeline. * [Workload, Capacity \& Worklogs](https://help.activitytimeline.com/at/basic-concepts-workload-capacity-involvement.md) --- how much time someone is *scheduled* for (workload), how much room they *have* (capacity), and what they've *actually logged* (worklogs). --- language: "en" --- # Jira Tasks & Custom Events ActivityTimeline shows two main types of items on the timeline: * **Jira tasks** * **Custom Events** Understanding the difference between them is important because they serve different purposes. ## Jira Tasks **Jira tasks** are issues (work items) synchronized from Jira into ActivityTimeline. During setup, tasks from enabled Jira projects are loaded into the app and become available for planning, depending on user permissions. In the Planner module, users can browse and search these issues in the left panel. By default, this panel shows issues updated within the last 30 days unless at least one filtering criteria is applied. ![1-20240911-123245.png](https://help.activitytimeline.com/__attachments/a_d569401693ed40dd0746dea43709b79d17ad6ac128b6023c7f693d8e5e693fe7/1-20240911-123245.png?cb=ebdc5d20422e7c6b6308c59508467ff0) Each Jira task appears as a separate item on the timeline that has a set of attributes that describes this task (*i.e. priority, issue type, estimate, etc* ), however, the appearance is customizable and can be adjusted according to the user's needs in *Configuration → Issues.* ![2-20240911-123245.png](https://help.activitytimeline.com/__attachments/a_5fe846634cf4193fb1fcadcde82c1d8dad9eaf566b88921ec5d5688f3b3bdc6c/2-20240911-123245.png?cb=957df69baf595eb24a43a452e7b49235) ## Custom Events **Custom events** are items created and stored directly in ActivityTimeline. They are useful for planning situations that are not fully covered by Jira work items, such as reserving time, marking time off, or adding non-project activities to the schedule. ![3-20240911-123245.png](https://help.activitytimeline.com/__attachments/a_876c1442004e977e374fb39c2b486c0e6c1b7e0daf3ddd3b4573e7fc1d0409c0/3-20240911-123245.png?cb=ca2c4b0ae7d450bcdcb582f29436432b) Here is the list of custom events that are available within ActivityTimeline. | **Name** | **Description** | |-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | BOOKING | Blocks persons' capacity for a certain number of hours per day. Allows to reserve/allocate person for certain activity/project, without specifying exact Jira tasks. | | DAY_OFF | Excludes the day from user's work schedule. System doesn't allocate the workload on the day with Day Off. You can either have 'Full day off' or 'Partial' for a specific number of hours. | | HOLIDAY | Event used to mark public holidays and official non-working days. Can be automatically created through 'Holiday scheme' | | NOTE | Item does not affect user's capacity and is a simple text message/reminder on a person's timeline. | | OVERTIME | Opposite to Booking, this event adds certain number of hours to user's capacity on a certain day. Recommended to use when the overtime is 'expected\&agreed' in advance, not to make the person overloaded. | | PLACEHOLDER | Can exist either as standalone item or be connected to Jira issue. Can be used to try different planning scenarios without actually changing Jira issues. Approving Placeholder creates an actual Jira task. | | SICK_LEAVE | This event tracks days when a user is off due to medical reasons. | | VACATION | Custom event to track users' vacations. Manager or Admin can approve vacations to restrict their editing by other users. | You can also create your own custom event types based on system event types, which gives you more flexibility in how you plan work. ![CleanShot 2025-05-29 at 18.14.49@2x-20250529-151458.png](https://help.activitytimeline.com/__attachments/a_b1e671be870e17573b1bcf250aa46cd4dedf0d10fbfe0dcec6f15ced47fdcbcb/CleanShot%202025-05-29%20at%2018.14.49@2x-20250529-151458.png?cb=d65af8c867db4b6e6af993e34566db8b) ## Why this matters Use **Jira tasks** for work that exists in Jira. Use **custom events** for planning items, availability changes, and activities that still affect the schedule but do not need to be regular Jira issues. --- language: "en" --- # Personal & Team Timelines The whole concept of timelines is quite old and pretty straightforward, as it simply allows to see how work (Jira issues) is spread across the period. ActivityTimeline takes this concept to a higher level, allowing to display the resources: individual users and teams in the dimension of time, while also taking into account the workload and the constraint of capacity of the available resources. ## Personal Timeline A **personal timeline** shows work planned for one person. This is the core view in ActivityTimeline. Each resource has their own timeline, where assigned and scheduled items appear. This helps managers and team members understand what work is planned and when it is expected to happen. Each resource within the application has its timelines, where tasks that are assigned and scheduled to him are displayed. ![1-20240911-123109.png](https://help.activitytimeline.com/__attachments/a_bf59c0a125e2d4a054ce73ade99b1a178798f983f22f680feb328ed0db2f01b7/1-20240911-123109.png?cb=ba4d4a65b15c14a9e5566077ce81ff7f) Under each person's name, ActivityTimeline also shows a **workload indicator**. This indicator reflects the hours allocated to that person based on scheduled issues and custom events. Its colors help you quickly understand how loaded that person is compared with their capacity. ![2-20240911-123110.png](https://help.activitytimeline.com/__attachments/a_da5c12e0ec5f2a24e78f718c44003931dc11d5554aa8c3decee2708ee6acd280/2-20240911-123110.png?cb=cb61e5956f16cb8103b9389521deba12) ## Team Timeline A **team timeline** shows work at team level instead of only at individual level. This view is useful when you want to plan work for the whole team before deciding exactly who will do it. It is especially helpful for longer-term planning, when details are still uncertain. You can switch between **Users** , **Teams and Team with Users view** from the selector in the top panel. ![CleanShot 2026-04-01 at 17.17.15@2x-20260401-141730.png](https://help.activitytimeline.com/__attachments/a_b83bd742edf2bcac23308a626674ccb2b01240fce125bd2334f0fe2687f23476/CleanShot%202026-04-01%20at%2017.17.15@2x-20260401-141730.png?cb=388ef67fafe59d04fc06139c174f224e) You can check the detailed guide on the Team panel in our documentation: [Team Panel](https://help.activitytimeline.com/at/team-panel.md) ## Why this matters Use the **personal timeline** when you need detailed planning for specific people. Use the **team timeline** when you want a broader planning view or are not ready to assign the work yet. --- language: "en" --- # Resources & Teams ActivityTimeline is built around planning work for people and groups of people. In the app, individual people are called **resources** , and groups of people are called **teams**. These two concepts are the foundation of planning in ActivityTimeline. ## Resources A **resource** is a person available in ActivityTimeline. In most cases, this means a user with access to Jira who appears in the app. Resources can also have additional information assigned to them, such as **roles** , **positions** , and **skills**. This helps you organize people and plan work more effectively. You can manage your resources in: *ActivityTimeline Configuration → Users:* ![CleanShot 2026-04-01 at 16.59.50@2x-20260401-140002.png](https://help.activitytimeline.com/__attachments/a_607a252b0c3a46080dff8dee45e374a54cc1881199095b1a45c7ffa0bf9b1f02/CleanShot%202026-04-01%20at%2016.59.50@2x-20260401-140002.png?cb=5b4a288bff106b9847891c3611f8c533) ## Teams A **team** is a group of resources that you want to manage and plan together. Teams help you look at work on a higher level instead of only person by person. There are 2 types of Teams in ActivityTimeline: Classic and Functional. The difference behind these two team types is the way how they are formed and maintained: * **Classic Team** is created by manually adding users to a team. This is the right option when you want full control over who belongs to the team and when membership changes. You can add or remove users at any time. ![2-20240911-122821.png](https://help.activitytimeline.com/__attachments/a_4652a60cf4a6e5b2ccb6292032ccf78a0484facc01d74a84a6cb0f1bb3b10a23/2-20240911-122821.png?cb=8cd1226160baed05955d5e993c5393a1) * **Functional Team** is created automatically based on user attributes, such as **skills** or **positions**. To use this type of team, you first [assign skills or positions to users.](https://help.activitytimeline.com/at/assign-users-to-roles-positions-and-skills.md) Then ActivityTimeline can build the team automatically based on that data. This is useful when team membership should be driven by employee capabilities rather than manual setup. ![3-20240911-122822.png](https://help.activitytimeline.com/__attachments/a_cbdc2c58b215a7f0f2e50339d483cb7d6787b07d0644b0fd2573c540f0f30e6b/3-20240911-122822.png?cb=c5ea660ae07b8aecea01b04364811e66) ![4-20240911-122821.png](https://help.activitytimeline.com/__attachments/a_17a7beac62cd696bbd6a3a11d7055edf8c99d7307773af1e286d58fd10dcec6f/4-20240911-122821.png?cb=40e1bb5aec69884de4a7fa1d52a27feb) ## Why this matters Once your resources and teams are set up, you can plan work more clearly, review capacity more easily, and report on progress at both individual and team level. ![CleanShot 2025-05-29 at 18.09.48@2x-20250529-150956.png](https://help.activitytimeline.com/__attachments/a_4a53188eead8a5b4307bc169a0b26b176701cf0e5661885a554e6d41a4883540/CleanShot%202025-05-29%20at%2018.09.48@2x-20250529-150956.png?cb=d52d78d1ff9a19fe3e69c9cc5786bf6e) --- language: "en" --- # Basic Concepts & Terms: Finances ActivityTimeline is a resource planning application, so the main focus of the Finances module is tying the activities of your individual resources and teams directly to project costs and revenue. Before you begin configuring your first financial tracker, it's essential to understand a few core concepts that dictate how money is calculated and allocated within the system. You can access the list of all your budgets in **ActivityTimeline → Finances:** ![CleanShot 2026-04-22 at 14.03.51@2x-20260422-110413.png](https://help.activitytimeline.com/__attachments/a_afad00208df6a29ff7ae26a86ee6f2d54a70d43d0b6fc974a00b851443b9043e/CleanShot%202026-04-22%20at%2014.03.51@2x-20260422-110413.png?cb=bdc4b2a1a6dee220a9274a5ce0074860) ## The Budget (Project) A concept of a Budget is pretty straightforward in ActivityTimeline. It acts as a primary **container** for a specific set of financial data. A Budget defines the boundaries of what you are tracking---connecting the financial targets you set in ActivityTimeline with the actual work happening in Jira. When you create a new Budget, you are essentially drawing a fence around a specific body of work to monitor its costs and revenue. There are three ways to define the scope of a Budget in ActivityTimeline: * **Jira Projects:** The budget tracks all issues and worklogs within one or multiple selected Jira Projects. * **Jira Epics:** The budget tracks all issues and sub-tasks belonging to one or multiple specific Epics, regardless of the overarching project. * **Jira JQL (Saved Filter):** For highly customized tracking (e.g., "All high-priority bugs assigned to the Dev Team this quarter"), the budget tracks any issues returned by a saved Jira filter. ![image-20260401-162612.png](https://help.activitytimeline.com/__attachments/a_9d67d4a7095205284e0911910753f280280ddba8d418ab7d729fd5ae01c733eb/image-20260401-162612.png?cb=dfa38c444380a292eaf3fbb40b5e5337) New budget create screen ### Financial Entities The Finances module revolves around three primary entities that determine your project's financial health: * **Budget (Planned):** This is the monetary cap or target assigned to a specific scope of work (like a Jira Project, Epic, or JQL filter). The budget can be a **Manual Budget** (a single fixed amount you enter) or an **Estimate-Based Budget** (automatically calculated by multiplying original task estimates by user cost rates). ![image-20260401-160523.png](https://help.activitytimeline.com/__attachments/a_55692b4b3e8ea03519cf4c117e03550ccf31979ac3c80bc3763f572a3e363a39/image-20260401-160523.png?cb=014121591a7926ea327211a60eba54e7) Admin can define how the budget is set up * **Actual Spend (Cost):** This is the true cost incurred by your team. It is calculated automatically by adding the cost of all worklogs (hours logged × the user's hourly cost rate) plus any manually entered fixed expenses (like software licenses or travel). ![image-20260401-160547.png](https://help.activitytimeline.com/__attachments/a_433afe7370498394e6ef167e7e878bd40bcf7e09b8eaea095b718998649bdf30/image-20260401-160547.png?cb=04b3517e89757b0676944eef3586b766) * **Actual Revenue:** This is the income generated by your team. It is calculated automatically by adding the value of all billable worklogs (hours logged × the user's hourly billing rate) plus any manually entered fixed revenue items. ![image-20260401-160941.png](https://help.activitytimeline.com/__attachments/a_e3df41018d85ca77c89cd89ebbcf8b9982b0040b026416162b3b89ade424bf11/image-20260401-160941.png?cb=18847e7be581cdba72f109f90727aa60) ### Labor Rates Labor rates are the engine of the Finances module. They convert the time your team logs in Jira into actionable cost and revenue data. To ensure accurate historical reporting, all rates in ActivityTimeline are **effective-dated**. This means a rate change only applies from a specific date onward, preserving the accuracy of past financial calculations. ![Screenshot 2026-04-01 at 17.11.48.png](https://help.activitytimeline.com/__attachments/a_700f055afe32bc0da4bc9de8731a8b1ead685c14e7517c4e6abe38a1786189cb/Screenshot%202026-04-01%20at%2017.11.48.png?cb=bd8179955217105215db8106ade0cf1c) Depending on the date of the worklog, the corresponding rate will be applied **Hourly vs. Monthly Rates** ActivityTimeline supports two distinct ways to calculate the financial impact of a team member: * **Hourly Rates:** The standard method. The system multiplies the specific hours logged on a Jira issue by the user's hourly rate. If they don't log time, no cost or revenue is generated. * **Monthly Rates:** A time-based method, often used for salaried employees or fixed retainers. A Monthly Rate is a fixed amount applied to the user for the calendar month, *which does not depend on the Jira worklogs* . The system automatically prorates this amount across the active days of the month. Learn more about how the labor rates work in [Labor Rates \& Rate Hierarchy](https://help.activitytimeline.com/at/labor-rates-rate-hierarchy.md) There is a strict **Rate Hierarchy** in ActivityTimeline. When calculating the cost or revenue of a specific worklog, the system looks for the most specific rate available on that date, in this order: 1. **Labor rate adjusted rate:** A rate assigned to a specific type of work/category (e.g., "Urgent work" or "Non-billable"). This overrides all other rates, and can be represented as an absolute value (e.g., non-billable billing rate is $0/hour for the end customer) or as a multiplier (e.g. Urgent work is **x3** the normal rate). ![image-20260401-161643.png](https://help.activitytimeline.com/__attachments/a_3959220310f15cb90033da98315a99aa0d8e8e804955822eb75df353d5708c55/image-20260401-161643.png?cb=cc8b7b8ac45d0a6880e39368f6e1c20d) Example of custom category rates 1. **User Rate:** A specific rate assigned to an individual team member. 2. **Default Budget Rate:** The fallback rate applied to the entire budget if no user or category rate exists. ### Budget Allocations (Targets) While your "Total Budget" might be a single number (e.g., $50,000), you often need to track spending against specific targets within that budget. This is done using **Budget Allocations**. Budget Allocations allow you to manually break down your total budget across custom dimensions (like Jira Categories, Components, or specific Assignees). ![CleanShot 2026-08-26 at 09.54.06@2x-20260826-085429.png](https://help.activitytimeline.com/__attachments/a_e827baaf386bb1afbc4f5a2cacbdbd152a837bc09466d114a915cfb8eccea2a0/CleanShot%202026-08-26%20at%2009.54.06@2x-20260826-085429.png?cb=1d39b0c657aba4d6a8087d319a7aca72) These manual allocations are crucial because they power the **"Budget" (Target)** side of your "Budget vs Spend" reports, allowing you to visually compare your strategic plan against the actual expenditure calculated from your team's worklogs. ![CleanShot 2026-08-31 at 13.17.40@2x-20260831-101747.png](https://help.activitytimeline.com/__attachments/a_edbb20c4f13b16e7e578e940a0890d1d0cafe0b6fd29a91deea89ca68fa0e105/CleanShot%202026-08-31%20at%2013.17.40@2x-20260831-101747.png?cb=bfc1f958c72a94ac3b539837081fd5a5) --- language: "en" --- # Workload, Capacity & Worklogs ActivityTimeline helps you answer three key questions: * How much work is planned? * Do we have enough time to complete it? * How much work has actually been done? To do this, the app uses three connected concepts: * **Workload** --- planned work * **Capacity** --- available time * **Worklogs** --- actual work Understanding how these work together is essential for planning and reporting in ActivityTimeline. ## Workload (Planned Work) **Workload** is the amount of estimated work assigned to a person for a selected period. It is based on: * Jira issue estimates (hours or story points), * custom events such as bookings or placeholders. When you assign and schedule a task, its estimate is distributed across the selected dates and added to the person's workload. The workload indicator shown under each resource is one of the fastest ways to review this. ![CleanShot 2026-04-01 at 17.40.48@2x-20260401-144100.png](https://help.activitytimeline.com/__attachments/a_8636e3c8b8d0ed88d97a4bd3de2081ae3af363d73897165076034c3adec171c3/CleanShot%202026-04-01%20at%2017.40.48@2x-20260401-144100.png?cb=f81bdf8d05c93feedfba5305423d8f8b) For the workload indicator to display the workload, tasks assigned to the resource must be estimated. ActivityTimeline can read both hours and story points estimation ([if conversion factor is determined](https://help.activitytimeline.com/at/customer-q-a-administration-configuration.md)). You can learn more about the workload indicator in our documentation: [Workload Indicator](https://help.activitytimeline.com/at/workload-indicator.md) ## Capacity (Available Time) **Capacity**is the amount of time a person is available to work. It is calculated based on: * involvement (for example, 8 hours per day), * time off (vacation, sick leave, holidays). Involvement can be set for the organization as a whole or individually for each resource and each day. ![image-20230109-142007.png](https://help.activitytimeline.com/__attachments/a_10d7df4b2ce96ab89b25ea676e4f03c4523b008eed9fae9bb77d2e3332339746/image-20230109-142007.png?cb=2afcd9694146739589f31d7c3de1da16) You can manage individual involvement for each resource in his/her User Management page under *Configuration → Users:* ![4-20240911-123612.png](https://help.activitytimeline.com/__attachments/a_d60d569e90bf23195bbb00506cc31d0bbd174d608c8cf9214d3b4fcfe1ed9aed/4-20240911-123612.png?cb=4f9bf91436d9e5ca1d414a562652cdc0) ## Worklogs (Actual Work) **Worklogs r**epresent the time that was actually spent on work. They come from: * time logged in Jira, * time logged directly in ActivityTimeline. Worklogs are used to track real effort and compare it with what was originally planned. Worklogs are viewed in Timesheet module but can also be displayed on the individual timeline in Planner when Worklogs \& Workload mode is enabled. ![CleanShot 2026-04-01 at 17.39.38@2x-20260401-143958.png](https://help.activitytimeline.com/__attachments/a_d93fbdfcca7efd8835f28e2f872c0ce109af450aa658cce84f08a13537f2d112/CleanShot%202026-04-01%20at%2017.39.38@2x-20260401-143958.png?cb=edc0fc768be1c929e7f6bccb7fbc2737) Worklogs items are available in ActivityTimeline in read-only format on the Planner. In the Workspace they can be drag'n'dropped or re-sized like Jira issues. ## Why This Matters These three concepts are always used together. ### 1. Workload vs Capacity → Planning ActivityTimeline compares workload with capacity to show whether a person is: * overloaded (too much work), * underloaded (not enough work), * or balanced. This helps you distribute work more effectively. ### 2. Workload vs Worklogs → Accuracy Comparing planned work with actual work helps you understand: * whether estimates are accurate, * where time is being underestimated or overestimated, * how planning can be improved. --- language: "en" --- # Booking Custom Event ## What is a Booking? A **Booking** is a custom event type in ActivityTimeline used to reserve a person's capacity for a specific number of hours per day. Bookings allow managers to allocate time for a project or activity without scheduling a specific Jira issue. ![CleanShot 2026-07-03 at 23.17.15@2x-20260703-201720.png](https://help.activitytimeline.com/__attachments/a_1d8e07a01f6bdaf2519282b9de74fb39ac8127b246ee2eb8a33e1924ba4cca0d/CleanShot%202026-07-03%20at%2023.17.15@2x-20260703-201720.png?cb=25598db40574106b6a219460fc0b1801) ### What are Bookings used for? Bookings are useful when you need to reserve capacity. Common use cases include: * reserving time for future work; * allocating a person to a project; * planning work when Jira issues are not created yet; * blocking capacity for internal activities; * preventing overbooking and scheduling conflicts. Bookings help managers keep a clear overview of resource availability and planned workload. ### Creating a Booking To create a Booking: 1. Click an empty cell on the user's timeline. 2. Select Booking in the Create New Item dialog. 3. Enter the **Booking** title. 4. Select a project, if needed. If no specific project is selected, the Booking can be created under General. 5. Set the number of **Hours per Day.** 6. Optionally, add an **External Link** and **Description**. 7. You can also select **Create for everyone in this team** to add the Booking to each team member's timeline for the selected period. 8. If needed, configure **Recurrence** (There is a limit of 100 events per recurring series). 9. Click **Create**. ![CleanShot 2026-07-03 at 22.53.14@2x-20260703-195824.png](https://help.activitytimeline.com/__attachments/a_ec3128c7db8f62522030ad08447979fc2b1557ff3356158fe338eb676951acf6/CleanShot%202026-07-03%20at%2022.53.14@2x-20260703-195824.png?cb=3353a0e47a290105d4884c614f1d89b1) ### Booking Approval Users with the required permissions, such as **Administrators** , **Managers** , or **Team Leads**, can approve Bookings. ![CleanShot 2024-07-25 at 16.30.31@2x-20240725-133041.png](https://help.activitytimeline.com/__attachments/a_4c05479912597530329eab22709f2af43bea7f37051a652b93559ea29a5e718f/CleanShot%202024-07-25%20at%2016.30.31@2x-20240725-133041.png?cb=fdd153c0e58287895f695b0ede8c07d6) Once approved, the approval icon changes color, and the Booking becomes locked. Employees and users with lower-level permissions will not be able to modify the Booking unless it is unapproved by an authorized user. To unapprove a Booking, click the same approval icon again. ### How Bookings Affect Workload Bookings are included in workload calculations. For example, if a user has an 8-hour Booking on a specific day, ActivityTimeline shows 8 hours of planned work in the workload indicator, even though no Jira issue is scheduled. ![CleanShot 2026-07-03 at 22.55.52@2x-20260703-195556.png](https://help.activitytimeline.com/__attachments/a_8fd617a4c73a0b8bb220a8264a7c251d24132c059bb14c10df03cf7f0af996ef/CleanShot%202026-07-03%20at%2022.55.52@2x-20260703-195556.png?cb=4c523ffaf88eab58e9ed4eb805cc02ea) This helps managers understand how much capacity is already reserved and avoid overbooking. ### FAQ **Q: How can I update a Booking?** **A:** Click the Booking once and select **Open** . Make the required changes and click **Update**. ![CleanShot 2026-07-14 at 12.25.28-20260714-092752.gif](https://help.activitytimeline.com/__attachments/a_377f3ddfe12a5503b6501b1626ddb3419c2b4662e4d31bc03dfb4946c199cbe0/CleanShot%202026-07-14%20at%2012.25.28-20260714-092752.gif?cb=298a25dfaef51849adbbd65749b1e86a) You can also update a Booking directly on the timeline: * drag and drop the Booking to change its date or move it to another user; * resize the Booking to change its duration. This makes it easy to quickly adjust Booking dates, duration, or assignee without opening the event details. **Q: How can I delete a Booking?** **A:** Click the Booking and select **Open → Delete.** ![CleanShot 2026-07-03 at 23.03.11@2x-20260703-200334.png](https://help.activitytimeline.com/__attachments/a_84bb949f4e64a8b48c64b579fe3306b0240427b0d762f4aba00d6f11408b3c51/CleanShot%202026-07-03%20at%2023.03.11@2x-20260703-200334.png?cb=08bf2aca126bf0b76466a1944698e58a) Alternatively, drag and drop the Booking to the Unscheduled section in the bottom-left corner. ![CleanShot 2026-07-03 at 23.05.36@2x-20260703-200551.png](https://help.activitytimeline.com/__attachments/a_b1bac894f96069971bff13b702f445f585a4a4e4de2a3977ba0f5290abd344d8/CleanShot%202026-07-03%20at%2023.05.36@2x-20260703-200551.png?cb=7be8e2457c3aafc0e8a3ff154c81924e) Please note that Booking events do not have a cache. Once deleted, the Booking is permanently removed. **Q: How can I delete a recurrent Booking?** **A:** Recurrent Bookings can be deleted by clicking the booking icon on the Booking event and selecting **'All recurrences'.** ![CleanShot 2026-07-03 at 23.07.16@2x-20260703-200733.png](https://help.activitytimeline.com/__attachments/a_8ea6cef57c49b455520ac8393cbe59977463846635e938651cef6d7f7b14bd6c/CleanShot%202026-07-03%20at%2023.07.16@2x-20260703-200733.png?cb=8c964d2ca7ce5a55a8aaec57128cc903) **Q: Do Bookings affect workload and forecasting reports?** **A:**Yes. Bookings are included in workload calculations and forecasting reports, helping managers understand planned capacity and allocation. **Q: Do Bookings appear in Timesheets?** **A:**Yes. By default, Bookings can be treated as time spent in Timesheets. ![CleanShot 2026-07-03 at 23.09.45@2x-20260703-201001.png](https://help.activitytimeline.com/__attachments/a_b2d3eba675abc8fcc7e75de516a3a9a5cca98157dc1b966671f9db032452fb03/CleanShot%202026-07-03%20at%2023.09.45@2x-20260703-201001.png?cb=4156e2c46b64dfa923aa95f9a2d26391) If needed, this behavior can be disabled so that Bookings are not included as worklogs under **Configurations → Timesheets Configuration → Treat Booking items as worklogs.** **Q: Can I clone a Booking?** **A:** Yes. You can clone Bookings using bulk options or by dragging and dropping the Booking while holding **Command** on macOS or **Ctrl** on Windows. ![CleanShot 2026-07-03 at 23.12.10-20260703-201246.gif](https://help.activitytimeline.com/__attachments/a_13d7a85f70c0802bfbf9edb47f7a0bc2ae59b2a12bce3726cfeb57754682af61/CleanShot%202026-07-03%20at%2023.12.10-20260703-201246.gif?cb=f282c5a53609ee2006a185ac7df248b7) **Q: Can I add notes or reference documents to a Booking?** **A:** Yes. Bookings support both **Description** and **External Link** fields, allowing you to include additional information or link to external documentation. **Q: Can I filter out timeline to see only Bookings?** **A:**Yes. Bookings can be filtered together with other timeline items using ActivityTimeline's filtering options using Type Filter and Apply Filters to Timeline option. ![CleanShot 2026-07-03 at 23.14.39@2x-20260703-201450.png](https://help.activitytimeline.com/__attachments/a_6ecfb2fbf6113c897a944b6644aac4faeb869f55f7250a161167fe0d44ed13bf/CleanShot%202026-07-03%20at%2023.14.39@2x-20260703-201450.png?cb=bb6ae15f57e531559362cd337ab36975) **Q: Can Bookings be created through the REST API?** **A:** Yes, Bookings as well as other custom events can be created via [REST API.](https://help.activitytimeline.com/at/rest-api.md) --- language: "en" --- # Bookmark Reports You can save a configured report as a **Bookmarked Report** and return to it later without rebuilding the report from scratch. ## Save a Report To bookmark a report: 1. Configure and generate the report you want to save. 2. Click **Bookmark**button. ![CleanShot 2026-07-23 at 15.59.10@2x-20260723-125941.png](https://help.activitytimeline.com/__attachments/a_6733f3db5f96e7bf389bb280afb87f0e75770c8bae9438c01996a33211506fbd/CleanShot%202026-07-23%20at%2015.59.10@2x-20260723-125941.png?cb=d7336b94f4e4b59736438e9c674fc980) 3. On the **Bookmark Report** page, review the inherited report settings, such as: * Report type * Units * First month * Period * Team * Other report-specific options 4. Enter a name in the **New report name** field. ![CleanShot 2026-07-23 at 16.01.01@2x-20260723-130107.png](https://help.activitytimeline.com/__attachments/a_7528ef68a684479909986b3cbba52391423ae0a85fa63acbaf87a2f1b1419ef5/CleanShot%202026-07-23%20at%2016.01.01@2x-20260723-130107.png?cb=0450216bce409ecbf701eee1893b5f84) 5. Click **Create**. The report is added to **Reports → Bookmarked tab**. ![CleanShot 2026-07-23 at 16.03.49@2x-20260723-130402.png](https://help.activitytimeline.com/__attachments/a_8aa5e0894562d6f2ba2084f3ee432043220448181919fa2846db6f7917ae645e/CleanShot%202026-07-23%20at%2016.03.49@2x-20260723-130402.png?cb=587c1c4d227c268bf6972b52f2cdef69) ## Open or Export a Bookmarked Report From the **Bookmarked Reports** list, you can open the saved report in: * **Web** format * **Excel** format This allows you to quickly regenerate the same report using its saved configuration. ## Share a Bookmarked Report By default, bookmarked reports are private to the user who created them. You can change the report's **Access Level** by clicking **Private** or the lock icon. The available access levels are: * **Private** --- Only the user who created the bookmark can view the report. * **Shared** --- The creator and other users with the link can view the report. ![CleanShot 2026-07-23 at 16.05.08@2x-20260723-130513.png](https://help.activitytimeline.com/__attachments/a_2c95460ffca3feda7250a2f2562ef59bfea20dbcec285fe8b547571ee5a9ddd1/CleanShot%202026-07-23%20at%2016.05.08@2x-20260723-130513.png?cb=493dc27859d732b2237b7f999a410215) To share a report, copy the link to the **Web Report** or **Excel Report** and send it to the required users. If the report is based on a Jira filter, users you share it with must also have access to that Jira filter. ## Delete a Bookmarked Report To remove a bookmarked report, open **Reports → Bookmarked** and click the delete icon for the report you want to remove. Deleting a bookmark removes the saved report configuration. It does not delete the underlying Jira or ActivityTimeline data. --- language: "en" --- # Budget Allocations While your "Total Budget" provides a high-level spending cap, effective financial management requires understanding how that money is distributed. The **Budget Allocations** configuration allows you to manually break down your total budget into specific, targeted sub-budgets. You define these targets based on custom dimensions (like Jira Categories, Components, or Assignees). These manual allocations are the engine that powers the **"Budget" (Target)** side of your [**Budget vs Spend**](https://help.activitytimeline.com/at/budget-vs-spend-report-finances.md)report, allowing you to visually compare your planned strategy against your team's actual expenditure. ![CleanShot 2026-08-31 at 13.23.56@2x-20260831-102401.png](https://help.activitytimeline.com/__attachments/a_590dc4cf7c14dcf4eca0009d71e573425b10ee8d8f84c61d9c651e5068aa3e9f/CleanShot%202026-08-31%20at%2013.23.56@2x-20260831-102401.png?cb=c68496ae4b8f3d480b4987506a764017) ## Setting Up Allocations To create your spending targets: 1. Navigate to the **Configurations** of your budget and select the **Budget Allocations** tab. 2. Click the blue **+ Add Allocations** button in the top right corner. 3. A pop-up will appear asking you to choose an **Allocation** dimension (the "Group by" field). Select the criteria you want to use for your targets (e.g., *Category* , *Component* , *Project* , or *Assignee*). 4. Click **Create**. ![CleanShot 2026-08-26 at 10.32.28@2x-20260826-093345.png](https://help.activitytimeline.com/__attachments/a_ae4fa0492888c05d285271aba9b20bc3ac826f0f455b6de3fa7922da256bdbe6/CleanShot%202026-08-26%20at%2010.32.28@2x-20260826-093345.png?cb=ba551d2101ed175934c8ce82d232a94d) ### Defining Sub-Budgets (Targets) Once you have added an allocation dimension (e.g., "Category"), you must define the specific targets within it. 1. Click the **+** icon on the right side of the newly added dimension row to add a specific item (e.g., if your dimension is "Category," add "Billable"). 2. For each item, you can define the target using either a fixed monetary amount or a percentage: * **Dimension Sub-Budget ($):** Enter the exact dollar amount you plan to spend on this item. * **Sub-Budget (%):** Enter the percentage of your Total Budget you plan to allocate to this item. 3. **Automatic Calculation:** When you enter a value in one field, the system automatically calculates and fills in the other based on your Total Budget. 4. Ensure that the **Summary** row at the bottom adds up to 100% of your Total Budget to avoid unallocated funds. 5. Click **Update** to save your allocations. ![image-20260402-152405.png](https://help.activitytimeline.com/__attachments/a_d0cf38de1a2ba89ff883a1b6bd04d6a2a98e7840c5b9710881ef57d476e290e7/image-20260402-152405.png?cb=afaf436abd27a9b22c31df3a0fa9d07d) *💡* ***Note:*** *You can create multiple allocation breakdowns for the same budget (e.g., one breakdown by Category and another breakdown by Component). You can then switch between these views in the "Budget vs Spend" report.* *💡* ***Note*** *: If actual spend occurs against something you haven't allocated for, that spend isn't lost --- it appears in a separate row in the Allocation Performance table, so your totals always reconcile even when your allocations are incomplete.* ### How Allocations Impact Reporting It is crucial to understand that the allocations you set here dictate what you see in the [**Budget vs Spend**](https://help.activitytimeline.com/at/budget-vs-spend-report-finances.md)report. **Understanding this report:** * **Budget (Left Chart):** Displays the manual targets you defined in this configuration screen. If you select a "Group by" dimension in the report that you *have not* configured here, the chart will display a "No Allocations Set" warning. * **Spend (Right Chart):** Calculates automatically based on your team's actual worklogs and logged expenses. * The **Allocation Performance** table combines both into one row per allocation --- Allocated Budget, Spend, % used, and what's remaining --- with a color-coded status (on track, fully spent, over budget) for each. By setting accurate Budget Allocations, you enable a powerful visual comparison: *"I planned to spend 70% of my budget on Billable work (Left Chart), but my team's actual time logged shows we've spent only 17% of our costs on Billable work (Right Chart)."* ### Chart Display Modes The **Budget vs Spend** view allows you to visualize the same financial data in two different ways. Use the chart switcher in the upper-right corner to move between **Pie Chart** and **Bar Chart** views. Both views use the same Budget and Spend data; only the way the information is visualized changes. #### **Pie Chart View** The **Pie Chart** displays **Budget** and **Spend** as two separate charts. ![CleanShot 2026-08-31 at 12.38.34@2x-20260831-093856.png](https://help.activitytimeline.com/__attachments/a_241eb8857f007d7dee98ea01780d55590166a9356f79e3fcfc4e98852852ef0f/CleanShot%202026-08-31%20at%2012.38.34@2x-20260831-093856.png?cb=a518781a9e5e3e357e7b4da0f94a078d) #### **Bar Chart View** The **Bar Chart** places **Budget and Spend side by side**, with each bar divided according to the selected grouping. ![CleanShot 2026-08-31 at 12.39.21@2x-20260831-094038.png](https://help.activitytimeline.com/__attachments/a_661aba83117badbb995202670691e7aa81693032015e308cafb5d05ddcc74a8a/CleanShot%202026-08-31%20at%2012.39.21@2x-20260831-094038.png?cb=348275922cd38ba69dfb261e75407dfd) Learn when to use each of the charts: [Budget vs Spend Report: Finances](https://help.activitytimeline.com/at/budget-vs-spend-report-finances.md) --- language: "en" --- # Budget vs Spend Report: Finances The **Budget vs Spend** report is the primary strategic comparison tool within the Finances module. It serves a single fundamental purpose:**to verify if project expenditure aligns with the strategic financial plan.** By visualizing manual targets against real-time expenditure, the report identifies specific work categories, teams, or individual projects that are consuming resources disproportionately or exceeding their absolute financial caps. ## Chart Display Modes The report provides two distinct ways to visualize the comparison between planning and reality. Use the **chart type switcher** in the top-right corner to toggle between these analytical views: ### 1. Proportional Analysis (Pie Charts) ![CleanShot 2026-08-31 at 12.38.34@2x-20260831-093856.png](https://help.activitytimeline.com/__attachments/a_0dff78bc243dd6093588787f6830e545a230715290c80c6d5390fae791fb2b2d/CleanShot%202026-08-31%20at%2012.38.34@2x-20260831-093856.png?cb=a518781a9e5e3e357e7b4da0f94a078d) This mode displays two side-by-side pie charts. It is designed for **relative comparison**, focusing on the distribution of the budget. * **Use Case:** Ideal for answering, *"* ***What percentage of our total effort is going toward Development vs. Support?"*** #### 2. Absolute Analysis (Stacked Bar Charts) ![CleanShot 2026-08-31 at 12.39.21@2x-20260831-094038.png](https://help.activitytimeline.com/__attachments/a_3849df7dfa192e35236de2b6b573a3789e20003761a0657e500a998cf9dfac43/CleanShot%202026-08-31%20at%2012.39.21@2x-20260831-094038.png?cb=348275922cd38ba69dfb261e75407dfd) This mode displays two side-by-side stacked bar charts where the **Y-axis represents the monetary value**. * **Use Case:** Ideal for comparing **actual money spent** against the planned budget in absolute terms. It allows managers to see if the total volume of spend is approaching the total budget limit, regardless of the internal proportions. ### Understanding the Charts The dashboard is divided into two main sections: your plan (left) and your reality (right). 1. **Budget (The Plan)** The left pie chart and table represent your **Planned Allocations**. * This data is **not** calculated from Jira estimates or worklogs. * It is drawn directly from the manual targets you configured in the [Budget Allocations](https://help.activitytimeline.com/at/budget-allocations.md) settings. * It shows how you *intended* to divide your Total Budget across the dimension currently selected in the "Group by" dropdown. *💡* ***Important:*** *If you have not configured Budget Allocations for the dimension currently selected in the "Group by" dropdown (e.g., if you group by "Component" but haven't set up component targets), this chart will display a "No data source" warning. Click the* ***Set Budget Allocations*** *button to define your targets.* ![image-20260427-142854.png](https://help.activitytimeline.com/__attachments/a_986df92e05eee78ede7b2e7ef2f72f289e254aef80af3cb60ee409d2a327673a/image-20260427-142854.png?cb=5445c48ec2aa2e5215b4521e41d2f067) 2. **Spend (The Reality)** #### Spend (The Reality) The right chart and table represent the **Actual Spend**. * **Source:** This is a real-time calculation summing all incurred costs: **(Logged Jira Hours ×** [**Applicable Cost Rate**](https://help.activitytimeline.com/at/labor-rates-rate-hierarchy.md)**) +** [**Manually Entered Fixed Expenses**](https://help.activitytimeline.com/at/manual-transactions.md). * **Function:** It automatically categorizes these costs based on the dimension selected in the "Group by" dropdown, allowing for an immediate audit of where money is actually flowing. ### Understanding the Allocation Performance Table Below the two charts, the **Allocation Performance** table gives you a row-by-row breakdown of every value in your selected "Group by" dimension --- combining what was planned and what's actually been spent. ![CleanShot 2026-08-31 at 12.41.44@2x-20260831-094152.png](https://help.activitytimeline.com/__attachments/a_2a7f29e71bc95af300c3aa7005b2ca2b6cddb7bc3dc9e90d46e817c57ac7ea35/CleanShot%202026-08-31%20at%2012.41.44@2x-20260831-094152.png?cb=b4460f9824e1b23e0bb0805adab1fca1) | Column | Value / Calculation | |--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Criteria** | The value for the selected "Group by" dimension (e.g., a specific Category, Project, or Assignee). | | **Allocated Budget ($)** | The manually configured sub-budget for this value, from Budget Allocations. | | **Allocation %** | `Allocated Budget / Total Budget × 100` | | **Spent ($)** | The actual cost incurred for this value. | | **Spend %** | `Spent / Total Spend × 100` | | **Budget Used** | `Spent / Allocated Budget × 100`, shown as a progress bar. The bar is **not capped at 100%** --- an exceeded allocation shows the real value (e.g., 115%), full and colored. | | **Remaining ($)** | `Allocated Budget − Spent`. **Not clamped at zero** --- an exceeded allocation shows as a negative value (e.g., −$5,000). | **Budget Used bar colors:** ![CleanShot 2026-08-31 at 12.42.51@2x-20260831-094256.png](https://help.activitytimeline.com/__attachments/a_4fafb481e1b3d37e619cc3975b14bd73d575499fba8aa44864ad9be69487d8f9/CleanShot%202026-08-31%20at%2012.42.51@2x-20260831-094256.png?cb=3750878aee9e952a13085e097db9469b) | Condition | Meaning | Color | |-----------------------------------|-------------|--------| | Spend = 0 | Not started | Grey | | 0 \< Spend \< Allocated Budget | On track | Blue | | Spend = Allocated Budget | Fully spent | Green | | Spend \> Allocated Budget | Over budget | Red | | Spend with no matching allocation | Unallocated | Orange | ### How to Use the "Group by" Filter? The true power of this report lies in the **Group by** dropdown on the left panel. By changing this selection, you change the lens through which you are analyzing your budget. ![CleanShot 2026-07-23 at 15.31.31@2x-20260723-123134.png](https://help.activitytimeline.com/__attachments/a_413168718ae745a06f1ce9fe31726d31589d0c3ddaaab1d3b4c8f0fe9e08f90a/CleanShot%202026-07-23%20at%2015.31.31@2x-20260723-123134.png?cb=a2f4790b7c8c28518686045b026e92c0) 1. **Select a Dimension:** Choose how you want to split your data (e.g., by *Category* , *Project* , *Epic* , or *Assignee*). 2. **Review the Plan:** The **Budget (Left)** chart will load the specific manual allocations you defined for that dimension in your settings. 3. **Analyze the Reality:** The **Spend (Right)** chart will automatically recalculate and re-group your actual costs based on that new dimension. ### **Example Use Case #1 (Pie Chart)** Let's say you allocated your $50,000 budget by **Category**, planning to spend not more than 20% on "Non-Billable" activities. You select "Category" from the Group by dropdown. The Left chart confirms your plan. However, the Right chart reveals that as of now the "non-billable" currently accounts for more than 32% of your actual spend. This visual discrepancy immediately alerts you that your team is spending too much time on Non-billable work and not enough on billable client projects, allowing you to take corrective action before the budget is exhausted. You'd see this instantly in the Allocation Performance table too: the "Non-Billable" row would show Allocation % 20% next to Spend % 32%, with a red Budget Used bar well past 100%. ![CleanShot 2026-08-31 at 12.51.55@2x-20260831-095254.png](https://help.activitytimeline.com/__attachments/a_092483c1dca1162ac9ced053509f1ba1eea35c288ec839c0956558902aab7964/CleanShot%202026-08-31%20at%2012.51.55@2x-20260831-095254.png?cb=ee7cf9f6b696d5bea8f8a0b6c998bddf) ### **Example Use Case #2 (Bar Chart vs Pie chart)** ### Analytical Example: The Danger of Relative Proportions Consider a scenario where a manager sets a total budget of **$100,000** with a strategic target to keep **Billable** work at **80% ($80,000)** of the total cost. * **Relative View (Pie Chart):** When checking the Spend pie chart, the manager sees that **82.39%** of the current spend is "Billable." At first glance, this suggests the project is healthy and exceeding the efficiency target. ![CleanShot 2026-08-31 at 12.54.46@2x-20260831-095508.png](https://help.activitytimeline.com/__attachments/a_58508ff73cdaacf72d05b771835e2e9b51fcfc7b4197b508c0a8cf05bbb68011/CleanShot%202026-08-31%20at%2012.54.46@2x-20260831-095508.png?cb=b35db4293550d586e7486db6c8dc2d32) * **Absolute View (Bar Chart):** Upon switching to the Bar Chart view, the Y-axis reveals a different reality. While the *proportion* of billable work is correct, the **Total Spend** has ballooned to **$123,429**. ![CleanShot 2026-08-31 at 12.55.25@2x-20260831-095533.png](https://help.activitytimeline.com/__attachments/a_fa1903a556720d2de2b28e17c23065c281f3e8cb76fa9de58670bbf04d52e940/CleanShot%202026-08-31%20at%2012.55.25@2x-20260831-095533.png?cb=2e317a83253ebecdf89e9c8479bc9cef) important **The Strategic Insight:** The pie chart masked the overspending because the ratio remained stable. The bar chart clarifies that the team has already spent **$101,699** on billable work alone---exceeding the entire intended billable budget by over **$21,000** . Without the absolute view, the manager might not have noticed that **the project has significantly exceeded its total financial cap**despite "meeting" its percentage-based efficiency goals. --- language: "en" --- # Bulk Mode & Refresh Users ## Bulk User Edit To simplify user management, ActivityTimeline provides **Bulk Mode** on the User Management page. Bulk Mode allows administrators to update user metadata for multiple users at once instead of editing each user individually. This is especially useful when managing larger teams or when you need to apply the same changes to many users. To activate Bulk Mode: 1. Go to **Configuration → Users**. 2. Enable the **Bulk Mode** toggle on the User Management page. ![CleanShot 2026-07-07 at 15.52.42@2x-20260707-125256.png](https://help.activitytimeline.com/__attachments/a_1afaf57c87ce5c9af3237ae818176a14056b0a66600df0edc2295773f298bc33/CleanShot%202026-07-07%20at%2015.52.42@2x-20260707-125256.png?cb=c7d095cd836dd4bf28a9b00b8d58e5c6) Once Bulk Mode is enabled, you can select multiple users and assign or remove user-related attributes in bulk, such as roles, positions, capacity, skills, or other available user settings. ![CleanShot 2026-07-07 at 15.54.41@2x-20260707-125446.png](https://help.activitytimeline.com/__attachments/a_7f0b4bf0302ecb6a9b9a26a3f3ce6762c2905b399ab97f2fee9b532642573b39/CleanShot%202026-07-07%20at%2015.54.41@2x-20260707-125446.png?cb=01b3a319939e42fa031c7a47e1cdaaf9) ## User Refresh If new users were created in Jira but have not yet appeared in ActivityTimeline, you can synchronize them manually. To refresh users: 1. Go to **Configuration → Users**. 2. Click **Refresh Users**. ![3-20240918-123602.png](https://help.activitytimeline.com/__attachments/a_77ff3b79bc1cb9d8ee83af2f505af400d581aa643658d3c4d1c2b0a9923bcb22/3-20240918-123602.png?cb=f26e43b58a2b04068750d91548fd039d) After clicking **Refresh Users** , you will be redirected to the **Synchronization** page. On this page, you can: * Run a manual user refresh. * Configure automatic user synchronization. * Define how often automatic user refresh should take place. * Set the default ActivityTimeline role for newly synchronized users. ![4-20240918-123602.png](https://help.activitytimeline.com/__attachments/a_2435cc2a5dd58b39ae9c6090b6fddf5d0ce31c715bf5d63ed3d46c9a11da09f0/4-20240918-123602.png?cb=577305ae4a35d2227bf41a1f4574a339) This helps keep the ActivityTimeline user list aligned with users from your Jira instance. --- language: "en" --- # Bulk Reschedule The **Bulk Reschedule** functionality allows managers to update multiple scheduled items at once instead of moving or editing each item manually. This is useful when a project is delayed, moved forward, put on hold, reassigned to another team member, or when several planned items need to be adjusted together. Bulk Reschedule can be used with items visible on the ActivityTimeline Planner, Bulk Reschedule functionality allows performing five main types of operations: * shifting issues forward or backward * unscheduling issues * reassigning issues to another user * cloning issues * approving / unapproving custom events Bulk Reschedule can be used with items visible on the ActivityTimeline Planner. Predefined non-working events, such as **Days Off** , **Holidays** , and **Sick Leaves**, are excluded from bulk rescheduling because they usually represent fixed availability changes rather than movable project work. ## Available Bulk Actions | **Action** | **Description** | |----------------------------------------|------------------------------------------------------------------------------| | **Move Forward** | Shifts selected items forward by a defined number of days, weeks, or years. | | **Move Backward** | Shifts selected items backward by a defined number of days, weeks, or years. | | **Unschedule** | Removes selected items from the timeline. | | **Reassign To** | Reassigns selected items to another user. | | **Clone To** | Clones selected items to another user. | | **Approve All** | Approves selected custom events. | | **Unapprove All** | Removes approval from selected custom events. | | **Replace Placeholder with Jira Task** | Replaces selected placeholders with actual Jira issues. | ## Where to Find Bulk Reschedule Bulk Reschedule can be opened in two ways. ### For a Whole Team To perform bulk actions for a team or a wider set of visible items, open the **Issue Panel** and go to: **Extra → Bulk Reschedule** ![1-20240916-104856.webp](https://help.activitytimeline.com/__attachments/a_5c98fe5bfa13886b97ac9106adb36f6aa484f8cebffb3527d525d2eed43bcab6/1-20240916-104856.webp?cb=66f5e3bd687d78d2988c75dfb3f5456c) This option is useful when you need to update items across a project, team, or selected timeline period. ### **For a Specific User** To perform bulk actions for one user, open the user's card: **Click the user's name → Bulk Reschedule** ![CleanShot 2026-07-09 at 16.12.21@2x-20260709-131245.png](https://help.activitytimeline.com/__attachments/a_b6e04c2dd7946222b473e8973d6acac1371b61b5205cac4b43a531fa40faa08e/CleanShot%202026-07-09%20at%2016.12.21@2x-20260709-131245.png?cb=40baef49a551a30a5e26fddc7b81981b) This option is useful when only one person's scheduled work needs to be moved, reassigned, cloned, or unscheduled. ## How Bulk Reschedule Works Bulk Reschedule updates all selected items as a single set of activities. For example, if a project is delayed by two weeks, you can move all related Jira issues, bookings, placeholders, and notes forward together instead of dragging each item separately on the timeline. The action is applied only to items that match the selected filters and criteria. ### **1. Choose Action** Select the operation you want to perform. ![CleanShot 2026-07-09 at 16.16.08@2x-20260709-131612.png](https://help.activitytimeline.com/__attachments/a_e0b22b498f55739f030246b2620d24ebacd60a9e765a572912f83b801a6dd1c4/CleanShot%202026-07-09%20at%2016.16.08@2x-20260709-131612.png?cb=a325ddd6f2670fc28db6d3d5f3061104) For **Move Forward By** and **Move Backward By**, define the number of days, weeks, or years. The default time unit is **weeks**. ### **2. Choose Team or User** Select whose timeline items should be affected. Available options may include: * **All Teams** * A specific team * A specific user ![CleanShot 2026-07-09 at 16.15.19@2x-20260709-131531.png](https://help.activitytimeline.com/__attachments/a_fc81d311f011d074077ff85a52f019dbe7a900a64e145a4fbd44f0b8662e9fcf/CleanShot%202026-07-09%20at%2016.15.19@2x-20260709-131531.png?cb=d29bad9a695dc5014f1c90672cab5f7e) This allows you to apply the action broadly or limit it to a particular resource. ### **3. Choose Project** Select which project should be affected. Available options: * **All Projects** * A specific project ![CleanShot 2026-07-09 at 16.16.31@2x-20260709-131640.png](https://help.activitytimeline.com/__attachments/a_9f596bf9ae2185a9f69bd42b084971d7768a4cd50cb9f8c0be39f85b8ea390e6/CleanShot%202026-07-09%20at%2016.16.31@2x-20260709-131640.png?cb=324458374a20777c4ccf846acc112587) This helps you limit the operation to items related to one project only. ### **4. Set Period** Specify the period using the **From** and **To** fields. ![CleanShot 2026-07-09 at 16.17.22@2x-20260709-131726.png](https://help.activitytimeline.com/__attachments/a_631ecf051c63b47f1adba58af05e3718946be0480c71bfb0dc1304a485da4049/CleanShot%202026-07-09%20at%2016.17.22@2x-20260709-131726.png?cb=db873cfb3b66e697d6fb1a2c611c1087) Only items within the selected date range will be included in the bulk operation. ### **5. Choose Item Type** Choose which types of items should be affected. Available item types include: * **Jira Issues** * **Placeholders** * **Bookings** * **Notes** ![CleanShot 2026-07-09 at 16.17.49@2x-20260709-131752.png](https://help.activitytimeline.com/__attachments/a_34f3db86edac65ab01459fcf56dad537df0be573f54ce71f3b5350250072bc78/CleanShot%202026-07-09%20at%2016.17.49@2x-20260709-131752.png?cb=12eedbb69bbef4f6e19846f2e1110ff9) For example, you can move only Jira issues while leaving bookings and notes unchanged. ### **6. Select Exact Items** After applying the filters, you can review and select the exact items that should be included in the operation. This gives you additional control before applying the bulk change. ![CleanShot 2026-07-09 at 16.18.30@2x-20260709-131834.png](https://help.activitytimeline.com/__attachments/a_d942f9a96736c92fd268bbaa74ea4c5dbd10c9e068105f42298d77b0ce93092f/CleanShot%202026-07-09%20at%2016.18.30@2x-20260709-131834.png?cb=f6c912fb91248634c7209af19404785a) ## **Important Notes** * Bulk Reschedule applies the selected action to the matching items visible on the timelines, starting from the first visible day and within the selected criteria. * The system can include Jira issues, placeholders, bookings, and notes, depending on the selected item types. * Days Off, Holidays, and Sick Leaves are excluded from bulk rescheduling. * Please note that the system does not automatically account for weekends when shifting items forward or backward. If items are moved across weekends, review the resulting schedule and adjust it if needed. *** ** * ** *** [CleanShot 2025-05-30 at 17.32.36.mp4](https://help.activitytimeline.com/__attachments/a_17db11548957e9c71f99c92e434023b09ebd01c2e9f0b9d37f4b32e3264f7d79/CleanShot%25202025-05-30%2520at%252017.32.36.mp4.md) Video Example of Bulk Reschedule --- language: "en" --- # Charts in ActivityTimeline ## Overview Starting from **version** v9.8.0+ ActivityTimeline includes several charts that help visualize planning, capacity, utilization, and project progress. Charts provide a quick graphical overview of key metrics and complement the detailed reports available in the Reports module. ![1-20240912-072535.png](https://help.activitytimeline.com/__attachments/a_6dc0c532aa4fec7bfd46b525b473be36bae36c6d12e4876cc92d10a24eae20eb/1-20240912-072535.png?cb=dc5340e250da574eeacb0fc44d87e0fe) ## Available Charts ### **Team Capacity Chart** Shows team capacity, allocated workload, and remaining availability across projects over time. ![image-20260705-200815.png](https://help.activitytimeline.com/__attachments/a_92c40b91d15f1506b867df078de29d39ac2702582d5d82907016abc6627550a6/image-20260705-200815.png?cb=e48cb8cab635984499f439f8013a3643) ### **Planned vs Actual Chart** Compares planned work with actual execution to help identify deviations and bottlenecks. ![image-20260705-200831.png](https://help.activitytimeline.com/__attachments/a_841cc334a44f70120a285eb697165926139d27b1d8dfbed597362a1a47338bd7/image-20260705-200831.png?cb=e0ae533004dc4b3f865e8117c3ec9749) ### **Team Utilization Pie Chart** Shows how team workload or time spent is distributed across projects for the selected period. ![image-20260705-200751.png](https://help.activitytimeline.com/__attachments/a_9fb61fc8e7aaed2028df9ab37f7275adce0d70bcb58fc4edbf51c647954119f2/image-20260705-200751.png?cb=fb745fa7029e26826056229967cc9d8e) ## **Learn More** Open each chart page to learn what it shows, how to configure it, and how to read the results. 1. [Team Capacity Chart](https://help.activitytimeline.com/at/team-capacity-chart.md) 2. [Planned vs. Actual Chart](https://help.activitytimeline.com/at/planned-vs-actual-chart.md) 3. [Team Utilization Pie Chart](https://help.activitytimeline.com/at/team-utilization-pie-chart.md) --- language: "en" --- # Classic Team Administration ## Classic Team A Classic Team is a group of people created by manually adding users into a single team. You can add or remove users from a Classic Team at any time. This team type is useful when you want full manual control over team structure and membership. Only users with the Admin or Manager role can create, access, or edit teams in ActivityTimeline. ![1-20240918-115913.png](https://help.activitytimeline.com/__attachments/a_402ce0e806de1971c23a3bf62392134918b870f8802f0e45ce6435afe1bd3620/1-20240918-115913.png?cb=f0053f00cbe80da9672867cc7c9a67be) ## Project Team If you already have a group of people in Jira working on tasks from a specific project and you would like to see them in ActivityTimeline grouped into a team, you can form a 'Project Team' that will work similarly to Classic Team but will be formed automatically by the system based on the users that are assigned to tickets from that project. For this go to*Configuration → Project → Click 'Create' next to the project name:* ![2-20240918-115913.png](https://help.activitytimeline.com/__attachments/a_aeaa22f93a6b7c6e72ce4fd2547cec946e605f08b97fb3e9b50a5280df36592b/2-20240918-115913.png?cb=0280106a13514fd1b263185df3cce809) ActivityTimeline will automatically suggest the team name, team members, and Team Manager based on the selected project. ![3-20240918-115913.png](https://help.activitytimeline.com/__attachments/a_1e55397995f8dd41c5c965db66de443ec2366bc6e17c96ae2f481aa285a913e2/3-20240918-115913.png?cb=eb2e46f603427fa5155fd8572074edd4) Once created, a Project Team is not updated automatically. Any future changes to team membership should be maintained manually, in the same way as for a Classic Team. For more information about teams in ActivityTimeline, see the **Basic Concepts:** [Resources \& Teams \| Teams](https://help.activitytimeline.com/at/basic-concepts-resources-teams.md#Teams) --- language: "en" --- # Clone Custom Events Custom events can be cloned to another day or to another person's timeline. This is useful when the same event needs to be added for multiple users or repeated on different dates. For example, if one team member has a day off on a specific date and another team member needs the same day off, the manager or the user can clone the existing event instead of creating it from scratch. There are two ways to clone a custom event to another day or another person's timeline: 1. Click on a cell and create a new custom event (regular way) 2. Drag and drop the custom event holding Control key (Windows) or Command key (Mac) and the system will clone the copies on this particular day off from one person's timeline to another. [1.mp4](https://help.activitytimeline.com/__attachments/a_e99eb87e999f0e4b53e2ba6642f4dd10040b5894460112599244d7e410d851e6/1.mp4.md?cb=fefe41cee25923c08f60ae73ffbaa481) You can clone a custom event multiple times if the same event needs to be added for several users or dates. --- language: "en" --- # Changing Issue Colors on the Timeline ActivityTimeline allows users to mark Jira issues and ActivityTimeline events with different colors on the Planner timeline. Color coding helps users visually highlight important work, distinguish between different types of tasks, and quickly identify items that require attention. ## Changing the Color of an Issue or Event To change the color of a Jira issue or ActivityTimeline event: 1. Click the issue or event on the Planner timeline. 2. Select the desired color from the available color options. ![CleanShot 2024-08-19 at 21.00.23@2x-20240819-180033.png](https://help.activitytimeline.com/__attachments/a_68fb4999265195fb27a4ba73c3243c14314feaa11fa2d07319707b194b0b7809/CleanShot%202024-08-19%20at%2021.00.23@2x-20240819-180033.png?cb=8a799aba9bad67d29e1b64ae755b6ddb) ActivityTimeline provides a standard palette of **12 colors**. Please note that this color set is predefined and cannot be customized. ### Using Colors for Prioritization Administrators can also create **Issue Customization** rules to apply specific colors automatically based on issue attributes. For example, tasks with the highest priority can always be displayed in a specific color on the Planner timeline. ![2-20240916-105424.png](https://help.activitytimeline.com/__attachments/a_153ab6a9df716bc32f8bf15bb3ac5450215f7164bd4f5a9e96ad4ee023020c12/2-20240916-105424.png?cb=8f3fc32c7161939ddac165f4e123d71f) To configure this, go to: **Configuration → Issues → Issue Customization** ![CleanShot 2026-07-09 at 16.56.39@2x-20260709-135658.png](https://help.activitytimeline.com/__attachments/a_5ffc65cbc18c76d7fc25cb81c64c280f416fbe1812a149df825dec678c01e027/CleanShot%202026-07-09%20at%2016.56.39@2x-20260709-135658.png?cb=4ef9e3b9bca3f19e044061e975de2201) ### Default Issue Color Administrators can also define the default color used for Jira issues on the timeline. To change the default issue color, go to: **Configuration → Timeline Panel → Default Color for Issues** ![CleanShot 2026-07-09 at 16.54.37@2x-20260709-135441.png](https://help.activitytimeline.com/__attachments/a_68890ea7e1cd33587a6be6f3d6b83609314851ece05a000fb68b078d227c84e1/CleanShot%202026-07-09%20at%2016.54.37@2x-20260709-135441.png?cb=f7c08b81a5a2f6cd2c3d0bb37fd650e2) This setting is available only to users with administrator permissions. --- language: "en" --- # Main Configuration The **Configuration** tab contains the main application settings and is the recommended starting point when setting up ActivityTimeline. This page gives administrators access to key setup areas, including general settings, Jira integration, timeline behavior, workload indicators, timesheet configuration, advanced settings, REST API settings, technical information, and the Setup Wizard. We recommend reviewing the main configuration settings first, as they define the core behavior of ActivityTimeline. After that, administrators can continue with more specific sections such as Teams, Projects, Users, Issues, Events, and Synchronization. ![1-20240919-081608.png](https://help.activitytimeline.com/__attachments/a_f04f72c7d9bc71ed78758f602b90a574334c3190c426756110f3a107b8fafb6c/1-20240919-081608.png?cb=c249f587bfe82bfa80fea5199c1b8dda) [Jira Integration Configuration](https://help.activitytimeline.com/at/jira-integration-page.md) [3rd Party Integrations](https://help.activitytimeline.com/at/3rd-party-integrations.md) * [Timeline Panel Configuration](https://help.activitytimeline.com/at/timeline-panel-settings.md) [Workload Indicator Configuration](https://help.activitytimeline.com/at/workload-indicator-configurations.md) [Timesheet Configuration](https://help.activitytimeline.com/at/timesheet-config.md) * [Finances Configurations](https://help.activitytimeline.com/at/daily-estimate-concept.md) * [Advanced Settings](https://help.activitytimeline.com/at/advanced-settings.md) * [AT REST API](https://help.activitytimeline.com/at/at-rest-api.md) * [Data Export/Import \| Migration from Data Center to Cloud](https://help.activitytimeline.com/at/data-export-import-migration-from-data-center-to-cloud.md) * [Setup Wizard](https://help.activitytimeline.com/at/setup-wizard.md) * [Dark Mode](https://help.activitytimeline.com/at/dark-mode-in-activitytimeline.md) --- language: "en" --- # Configure Story Points Conversion into Hours ## What are Story Points (SP)? Story Points are a unit of measure used in Agile project management and development to estimate the effort required to complete a task or a user story. Unlike hours, which measure time directly, Story Points are relative and abstract, representing the overall effort, complexity, and uncertainty involved in completing a task. Teams typically use a Fibonacci-like sequence (e.g., 1, 2, 3, 5, 8, 13, etc.) to assign Story Points to tasks. ### Converting Story Points to Hours To make effective use of the Workload Indicator in ActivityTimeline, converting Story Points to hours is necessary. This conversion helps translate the abstract measure of effort into a concrete measure of time that can be used for planning and resource management. Here are some steps to do this conversion: 1. **Establish a Baseline:** Determine a baseline for what a single Story Point represents in terms of hours. This can be done by reviewing past tasks and their completion times. 2. **Consistency in Estimation:**Ensure that the team consistently applies the baseline when assigning Story Points to new tasks. 3. **Regular Review and Adjustment:** Periodically review and adjust the baseline as needed based on actual work completed and any changes in team performance or task complexity. ### Example Conversion If your team determines that 1 Story Point generally equals 8 hours of work, you can use this baseline to convert Story Points into hours for planning purposes. For instance: * A task estimated at 8 Story Points would be converted to 64 hours. ![1-20240918-124600.png](https://help.activitytimeline.com/__attachments/a_e129686fae87936127625124702ad4d949f65851db2a41ea36107e1b70300153/1-20240918-124600.png?cb=7668c6f0ab875ed3b2a709c2f5a1741b) ### Benefits of Conversion 1. Converting Story Points to hours allows managers to create more accurate ActivityTimeline Resource Reports, ensuring that team members are not over or under-allocated. 2. The Workload Indicator can more effectively reflect the actual capacity and workload of team members, helping to balance work distribution. 3. Hours-based reporting aligns with many stakeholders' expectations and provides a clearer picture of progress and resource utilization. ### Conversion Factor Setting There are 2 conversion settings in ActivityTimeline: **Global** \& **Project**. This means you could have the same conversion for all projects or individual conversion for separate projects. ![2-20240918-124600.png](https://help.activitytimeline.com/__attachments/a_18543485553a32b706e867940b3ac2ea833fde4b94ad40a47109a5c48a92538a/2-20240918-124600.png?cb=923fe48a1f4e3fa98970a7a1cb43c70c) To configure a**Global** conversion factorgo to *Configuration → General → Define the conversion rate.* *This conversion will be applied to all projects that have estimation in Story Points* ![3-20240918-124600.png](https://help.activitytimeline.com/__attachments/a_418507f61eaa28f9c6a7ee3ae19a56f0336306e2650e952eda260bb0a34d837e/3-20240918-124600.png?cb=7a1056ece9758961db45bdfc43f398a6) To configure a**Project** conversion factorgo to *Configuration → Projects → Click "Manage" near the project name → Define the conversion rate.*This conversion will only be applied to a single project. If you have both Global Conversion \& Project conversion set up, the system will use Project Conversion Factor as the primary conversion parameter. Estimates will still be displayed in Story Points on the tasks regardless if you configure the conversion or not but if no conversion factor is set the workload won't be calculated. If you're estimating tasks with **Story Points** , make sure to select the **'Users do log worked time' option** in ActivityTimeline General Configurations**.** This is important because Story Points represent the effort needed for a task and don't change over time, unlike hours. So, even if the user logs time, Story Points will stay the same and need to be spread out over the task's duration. --- language: "en" --- # Cost/ Billing Rate Hierarchy To handle real-world financial complexity, ActivityTimeline uses a strict priority system when calculating the cost or revenue of a specific worklog. The system always looks for the **most specific rate available** on the date the work was logged, following this order: 1. **Category Rate (Highest Priority):** A rate assigned to a specific type of work (e.g., "Development" or "Urgent Support"). This overrides all other rates, including user-specific rates. 2. **User Rate (Medium Priority):** A specific rate assigned to an individual team member (e.g., "Senior Developer vs. Junior Developer"). This overrides the Default Budget Rate. 3. **Default Budget Rate (Lowest Priority):** The fallback rate applied if no Category or User rate exists for that specific worklog. ![image-20260826-094945.png](https://help.activitytimeline.com/__attachments/a_08524917a7e1faec28a42ee359f1182ebfff284423be38ac21d5e19d9fc6274c/image-20260826-094945.png?cb=5ef2599061d926a56a563991d8ad4a2a) --- language: "en" --- # Certified Professional Course To help you harness the full power of ActivityTimeline, we created the**ActivityTimeline Administrator Guide: Mastering Resource Planning and Time Tracking.** ![1-20240913-072722.webp](https://help.activitytimeline.com/__attachments/a_1567bc54d7664f1edfd05c15caf88c22e1011eb8ee6704f5e09cf34a81fa1371/1-20240913-072722.webp?cb=c769655927d40463db33fb47e9741348) ## Why does this course exist? Administrators and solution partners often need comprehensive training to fully understand all that ActivityTimeline has to offer. This structured guide walks you through every feature of the tool, ensuring you gain the confidence to manage it like a pro. ## Breakdown of the course content: This course covers the following content: * **Introduction to ActivityTimeline** * **Planner Module**: Learn about Capacity Planning and Planner's main features * **User Management**: Roles, Positions, Skills, Workload Schemes, and more * **Team Management**: Functional and Classic Teams, handling Imported Teams * **Effective Planning**: Planner Module, issue splitting, and planning on team levels * **Workload \| How to book users' time?**: Workload indicators, integration with Jira * **Sprints and Story Points**: Sprint planning, story points, and more * **Workspace Module**: Configuration and importance of workspaces * **Timesheets and Time Tracking**: Time tracking methods, workload calculation * **Reports and Analytics Module**: Charts, bookmarks, and gadgets * **3rd Party Integrations**: Webhooks, calendar integration, advanced settings Quizzes after each section will help you review what you've learned. ![2-20240913-072709.png](https://help.activitytimeline.com/__attachments/a_471bb046d68d6b37af6d8a79216b0ce97952e9aaaf77a48580db28bbaa47584f/2-20240913-072709.png?cb=7149141609cf78fd369a2a4833088106) By the end of the course, you'll have the expertise to fully optimize and manage ActivityTimeline, enabling seamless operation for your organization or customers. ## How to Enroll? To enroll, send an email to**support@reliex.com** with the subject "Course Enrollment." Upon enrollment, you will be sent an email invitation to access the course. Simply click on the 'Go to course' link to be redirected to the course page. Feel free to begin, pause, and resume the course at your own pace, as there is no time restriction. ![3-20240913-072710.png](https://help.activitytimeline.com/__attachments/a_0878813ffc5e03bf0de937d879795b7b78d457f9e32957b4e57ed641de3f5b4c/3-20240913-072710.png?cb=b349640c6c82624c38ab1bda2ebf77d1) ## How to Get Certificate? Upon successful completion of the course, you will be sent an email containing the certificate of completion. This certificate can be used to demonstrate your proficiency in ActivityTimeline. ![4-20240913-072721.webp](https://help.activitytimeline.com/__attachments/a_90d8fb6aa8fc2752fbd1d71befd55b16981b31d37600a33cdb36b6d75f868383/4-20240913-072721.webp?cb=6c386a553c958d5594ea76fd9de2b808) --- language: "en" --- # Create and Manage Custom Events ## Creating a Custom Event To create a custom event to a user's timeline, use one of the following options: * Click an empty cell on the user's timeline. * Click a cell that already contains scheduled tasks or events. * Click the **New Task** button in the top-right corner of the Planner. In the **Create New Item** dialog, select the required event type and fill in the event details. ![CleanShot 2026-07-13 at 17.51.12@2x-20260713-145117.png](https://help.activitytimeline.com/__attachments/a_1b61f1bd8587f787fe00d8d0895cf298269ce80b5ab87fa78c6fad4da321e87c/CleanShot%202026-07-13%20at%2017.51.12@2x-20260713-145117.png?cb=3b7ad424da8df94eda48531808c8db3b) Depending on the selected event type, you may be able to define additional information, such as duration, description, recurrence, linked Jira issue, or other event-specific settings. ## How Events Affect Workload and Available Capacity ActivityTimeline automatically updates workload and availability indicators based on the events scheduled on a user's timeline. For example, if a full-day **Day Off** event is added for Monday, the user's available capacity for that day is reduced. As a result, the workload indicator is recalculated to reflect that the user is not available for work on Monday. ![image-20230125-134808.png](https://help.activitytimeline.com/__attachments/a_e51a6011759610eb001dad970884ccd1fdc65fa75d378ae0061530ae089fd7ac/image-20230125-134808.png?cb=f149ff2f05479e974c1c9efd4c6d2402) Depending on the scheduled tasks, estimates, and workload calculation settings, remaining work may be redistributed across the user's other available working days. This helps managers immediately see how vacations, sick leaves, days off, bookings, and other events affect the user's capacity and schedule. ## Unscheduling or Deleting a Custom Event To remove a custom event from the Planner, drag and drop the event from the timeline to the **Unschedule** box. For Jira issues, this action usually removes the issue from the timeline and places it back into the unscheduled area. For ActivityTimeline custom events, this action deletes the event from the timeline. ![CleanShot 2026-07-13 at 17.56.00-20260713-145630.gif](https://help.activitytimeline.com/__attachments/a_416a27ae91363c8204397b65617033ecac2e143d02cd69fe8e7c545de5567a29/CleanShot%202026-07-13%20at%2017.56.00-20260713-145630.gif?cb=6facb6c40cde1231f364727470170be6) ## Managing Event Types Administrators can manage available event types, customize their appearance, and configure additional event settings. Learn more: [Custom Event Types](https://help.activitytimeline.com/at/new-custom-event-types.md) , [Issues and Events Configuration](https://help.activitytimeline.com/at/issues-and-events.md) , [Issue \& Event Appearance](https://help.activitytimeline.com/at/issue-event-appearance.md) --- language: "en" --- # Create Jira Issue from ActivityTimeline ActivityTimeline allows you to create Jira issues directly from the Planner, without switching back to Jira. This is useful when you identify missing work during planning and want to create and schedule a new issue right away. ## Creating Jira Issue from ActivityTimeline There are two ways to create the Jira issue on the person's timeline: * by clicking on a **New Task** to create a new Jira issue from the Planner toolbar. * by simply clicking on an empty timeline cell, or a cell where tasks are already scheduled, to create a new item for that specific date and user. ![CleanShot 2025-05-30 at 17.11.43@2x-20250530-141245.png](https://help.activitytimeline.com/__attachments/a_f1dbc0dc70695add7945407a1223be967402fab1cd55f94c50740d58ff658884/CleanShot%202025-05-30%20at%2017.11.43@2x-20250530-141245.png?cb=2660d3c315dfad27d90ef2b9b4c2cee2) In the **Create New Item** dialog, select the **Create New Issue** tab. ![1-20240916-101922.png](https://help.activitytimeline.com/__attachments/a_c49e690ecd5436c5413d0f2213ed2b873f1f666ccc1dccaeee99b67628962aae/1-20240916-101922.png?cb=6fe2c1bad1fefc9180372230facd48e5) Then fill in the required issue details: 1. Select a **Project** . The available fields are loaded based on the selected project and its Jira configuration. 2. Select an **Issue Type** . This field is required. 3. Enter the issue **Summary** . This field is required. 4. Fill in any additional fields, such as **Assignee** or **Description**, if needed. 5. Click **Create**. Once created, the issue is synchronized with Jira. ### Start and End Dates The start and end dates are set automatically based on how the issue is created. If you click the **New Task** button, the issue is created for the current day. If you click a specific timeline cell, the issue is created for the date of that cell. ActivityTimeline remembers the last selected **Project** and **Issue Type**. The next time you open the Jira issue creation dialog, these fields will already be pre-filled, helping you create similar issues faster. ### Configure Fields in the Create Issue Dialog Users can customize which fields are shown in the **Create New Issue** dialog and define their display order. ![2-20240916-101922.png](https://help.activitytimeline.com/__attachments/a_b2bfc28d9120e333eb514296c682a59e724c5afcf4f817d9bb0035a8d11258a9/2-20240916-101922.png?cb=80760cd12372ed871cd673e97dc78f01) This helps each user adjust the issue creation form to their planning workflow and keep only the most relevant fields visible. ## Creating Jira Issues Through the Jira Dialog The native Jira **Create** button is always visible in Jira, including when users are working in the ActivityTimeline Planner. ![CleanShot 2026-07-09 at 15.34.07@2x-20260709-123423.png](https://help.activitytimeline.com/__attachments/a_d328847cac9918d72bad3beee38aef1b63f74b084b844993df93f91fd42c72f4/CleanShot%202026-07-09%20at%2015.34.07@2x-20260709-123423.png?cb=138d23443b8075665cc4ee28a602ae69) When users click this button, the standard Jira issue creation dialog opens. The issue is created in Jira first, using Jira's own fields, required field rules, permissions, and validation settings. After the issue is created in Jira, click **Refresh** in ActivityTimeline to load the new issue into the Planner. Please note that this Jira **Create** button is separate from ActivityTimeline's **New Task** button. Administrators can enable or restrict issue creation through ActivityTimeline's own dialog in: **Configuration → Timeline Panel → Create Jira issues through ActivityTimeline** This setting controls whether users can create Jira issues directly from the ActivityTimeline **New Task** flow. --- language: "en" --- # Create Your First Team There are different ways to create teams in ActivityTimeline. For the initial setup, we recommend starting with a simple **Classic Team**. This makes it easier to understand the main features of the app before moving to more advanced team configuration. Once you are familiar with the basic planning flow, you can also try [**Functional Teams**](https://help.activitytimeline.com/at/functional-dynamic-team-administration.md), which provide more flexibility by grouping users based on attributes such as skills or positions. ## Setup Classic Team After installing ActivityTimeline and completing the Setup Wizard, you will see your dashboard with users and Jira tasks. At this point, the best next step is to create your first team. ![CleanShot 2025-09-30 at 15.38.09@2x-20250930-123817.png](https://help.activitytimeline.com/__attachments/a_41e29e4bc10bb9b4778333d4f8654f8513b169405ecc6ede0431f28617838a98/CleanShot%202025-09-30%20at%2015.38.09@2x-20250930-123817.png?cb=e2a5a599397cf4f1de9c8e7aeaafab80) Go to: **ActivityTimeline Configuration → Teams** ![CleanShot 2025-09-30 at 15.40.53@2x-20250930-124136.png](https://help.activitytimeline.com/__attachments/a_ca2ebb3ab1e7291448a53d651def9a46f7020e0d7a13f614ced4b38fe886389f/CleanShot%202025-09-30%20at%2015.40.53@2x-20250930-124136.png?cb=ce5ea1c0078cdcdbf3dfbee60f86a039) Then: 1. Click **Create New Team**. 2. Enter the team name. 3. Add users to the team by dragging them into the team area or by clicking the **+** icon. 4. Click **Create**. Your first team is now ready. ![CleanShot 2025-09-30 at 15.42.27@2x-20250930-124302.png](https://help.activitytimeline.com/__attachments/a_f263266dafc24c7d44a2ba5ace4e3ebb53a03c13a2ac0e3bb41299ecdb60f9ad/CleanShot%202025-09-30%20at%2015.42.27@2x-20250930-124302.png?cb=cc8c84068b0b8148a5f21ba98fd3f89a) ## Optional Settings Linking a project to a team and assigning a Team Lead is optional. Project linking is mainly used for additional context and better usability. For example, it can help filter Planner data by the team associated with a Jira project when ActivityTimeline is opened from that project page. ## What Happens Next Once created, the team becomes available across ActivityTimeline modules, including Planner, Workspace, Timesheet, and Reports. ![CleanShot 2025-09-30 at 15.46.47@2x-20250930-124701.png](https://help.activitytimeline.com/__attachments/a_906ba78635a44642056b93e345827c7a7b58525f6f9b6fc66cbffa476a00ea5e/CleanShot%202025-09-30%20at%2015.46.47@2x-20250930-124701.png?cb=730cc2ab5ff3193570751575c73344ff) You can now continue to the next setup step: [Assign Users to Roles, Positions and Skills](https://help.activitytimeline.com/at/assign-users-to-roles-positions-and-skills.md) --- language: "en" --- # Custom Events in ActivityTimeline In addition to Jira issues, ActivityTimeline allows users to create different types of custom events directly on the Planner. These events help managers and teams plan resource availability, reserve capacity, and track non-project activities that may not be represented by Jira issues. ![CleanShot 2026-07-13 at 17.47.53-20260713-144937.gif](https://help.activitytimeline.com/__attachments/a_c1ae05d9e9d6d6cc31eeec5aa60a588fff438d58ad45733d38c2afc0db593dd4/CleanShot%202026-07-13%20at%2017.47.53-20260713-144937.gif?cb=69aef3215666d871d03094fad27580ac) ActivityTimeline events can be divided into two main categories: * **Non-working events** * **Planning events** ## Non-working Events Non-working events are used to mark periods when users are not available for work. ![CleanShot 2026-07-13 at 17.45.28@2x-20260713-144535.png](https://help.activitytimeline.com/__attachments/a_e28c60e55b5f76f21c3c2c1dc65ccb28d6baf4560a906db3614a151ae3d17322/CleanShot%202026-07-13%20at%2017.45.28@2x-20260713-144535.png?cb=d588041c759938236cbd882b121b37cc) Examples include: * vacation; * sick leave; * days off; * holidays. Non-working events reduce the user's available capacity for the selected period. This helps managers understand real availability and plan work more accurately. For example, if a user has 8 hours of daily capacity and a full-day vacation is scheduled, ActivityTimeline reduces the user's available capacity for that day. Learn more: [https://activitytimeline.atlassian.net/wiki/spaces/AHC/pages/3773517322?xpis=eyJicmlkZ2UiOiJzbWFydExpbmtzIiwiaWQiOiIxNzgzOTQ4Mjk5NDkzIiwic291cmNlIjoiY29uZmx1ZW5jZSJ9](https://help.activitytimeline.com/at/time-off-management-holidays-vacations-sick-leaves.md) ## Planning Events Planning events are used to reserve or allocate a user's time for specific work, activities, or resource needs. They are useful when work needs to be planned, but a Jira issue is not yet available or does not fully represent the planned activity. ![CleanShot 2026-07-13 at 17.46.45@2x-20260713-144649.png](https://help.activitytimeline.com/__attachments/a_1398487696b77c0b5e55ff0d5f7231fcd5a423eca31176905d72667a5b07f3c8/CleanShot%202026-07-13%20at%2017.46.45@2x-20260713-144649.png?cb=f9ee5726a15669ade7e55fcead74291b) Planning events help managers allocate resources, forecast workload, and make sure the right people are available for planned work. Learn more: 1. [Booking Custom Event](https://help.activitytimeline.com/at/booking-event-type.md) 2. [Placeholder Custom Event](https://help.activitytimeline.com/at/placeholder-event-type.md) 3. [Overtime Event Type](https://help.activitytimeline.com/at/overtime-event-type.md) ## Note Event A **Note** event is used as a simple text note or reminder on a person's timeline. Note events do not affect the user's capacity, workload, or availability. They are intended for informational purposes only. ## Why Use Events Together with Jira Issues? Jira issues usually represent planned project work, while ActivityTimeline events help cover availability, resource reservations, and non-project activities. Using Jira issues together with ActivityTimeline events gives managers a more complete view of: * what work is planned; * who is available; * who is unavailable; * where capacity is already reserved; * whether users are overbooked or underutilized. This helps teams improve resource planning, capacity forecasting, and timeline accuracy. * [Create and Manage Custom Events](https://help.activitytimeline.com/at/create-and-manage-custom-events.md) * [Clone Custom Events](https://help.activitytimeline.com/at/clone-custom-events.md) * [Booking Custom Event](https://help.activitytimeline.com/at/booking-event-type.md) * [Placeholder Custom Event](https://help.activitytimeline.com/at/placeholder-event-type.md) * [Overtime Custom Event](https://help.activitytimeline.com/at/overtime-event-type.md) * [Time Off Management (Holidays, Vacations, Sick Leaves, Days Off)](https://help.activitytimeline.com/at/time-off-management-holidays-vacations-sick-leaves.md) --- language: "en" --- # Custom Styles ActivityTimeline allows administrators to configure custom styles for Jira issues and ActivityTimeline events displayed on the Planner timeline. Custom styles help visually distinguish different types of work and make the timeline easier to read. You can customize the appearance of items by changing their text color, background color, and font style. ## Issue Customization Custom styles for Jira issues can be configured based on issue-related attributes, such as: * Project * Assignee * Priority * Status To create a custom style for Jira issues, go to: **ActivityTimeline Configuration → Issues → Issue Customization → Add New Custom Style** ![CleanShot 2026-07-07 at 16.28.41@2x-20260707-132848.png](https://help.activitytimeline.com/__attachments/a_431fe314af406868524d5ff80ba5146a2a003b4463769106ec15e6ae0d950935/CleanShot%202026-07-07%20at%2016.28.41@2x-20260707-132848.png?cb=8a8b75c3ecf188d6924582487ee5a816) ![2-20240918-130153.png](https://help.activitytimeline.com/__attachments/a_b4c0eb814af86526fbbe8f86a69394e116b4b098132ecf021975b754586bceb3/2-20240918-130153.png?cb=7e6e8f705920603fe19dec45bd82e8dc) After the style is created, matching issue cards will be displayed on the timeline according to the selected style rules. ### Event Customization Custom styles can also be configured for ActivityTimeline events. Event styles can be based on the **Event Type**, allowing you to visually separate bookings, meetings, vacations, sick leaves, placeholders, or other custom event types. To configure styles for events, go to: **ActivityTimeline Configuration → Events → Event Customization** ![CleanShot 2026-07-07 at 16.28.18@2x-20260707-132825.png](https://help.activitytimeline.com/__attachments/a_396ea87301a1d2528af78d1d86db1aec87d84bab013389ce1058cca90940d4a6/CleanShot%202026-07-07%20at%2016.28.18@2x-20260707-132825.png?cb=15aa75166246cf1d00b22251f53e5bab) Using custom styles helps teams create a more visual planning experience and quickly identify important work items directly on the timeline. --- language: "en" --- # Common Questions & Answers This page contains the list of frequently asked questions and the answers to them. * [FAQ -- Planner](https://help.activitytimeline.com/at/customer-q-a-plan-main-dashboard.md) * [FAQ -- Issue Panel \& Filters](https://help.activitytimeline.com/at/customer-q-a-plan-issue-panel-filters.md) * [FAQ -- Custom events](https://help.activitytimeline.com/at/customer-q-a-plan-custom-events.md) * [FAQ -- Workspace](https://help.activitytimeline.com/at/customer-q-a-work-my-workspace.md) * [FAQ -- Timesheets](https://help.activitytimeline.com/at/customer-q-a-track-team-timesheets.md) * [FAQ -- Reports \& Analytics](https://help.activitytimeline.com/at/customer-q-a-report-analytics.md) * [FAQ -- User Management](https://help.activitytimeline.com/at/customer-q-a-user-management.md) * [FAQ -- Team Management](https://help.activitytimeline.com/at/customer-q-a-team-management.md) * [FAQ -- Project Management](https://help.activitytimeline.com/at/customer-q-a-project-management.md) * [FAQ -- Administration \& Configuration](https://help.activitytimeline.com/at/customer-q-a-administration-configuration.md) * [FAQ -- REST API](https://help.activitytimeline.com/at/customer-q-a-rest-api.md) * [FAQ -- Security](https://help.activitytimeline.com/at/customer-q-a-security.md) * [FAQ -- Legacy Version Setup](https://help.activitytimeline.com/at/customer-q-a-legacy-version-setup.md) * [FAQ -- Licensing and Purchase](https://help.activitytimeline.com/at/customer-q-a-licensing-and-purchase.md) --- language: "en" --- # FAQ – Administration & Configuration ## Does ActivityTimeline support other working days other than Mon-Fri? Yes, it is possible to change which days should be considered as working by the system, for this go to *ActivityTimeline Configuration → Workload Indicator → Change 'Work days'* configuration: ![image-20220311-135619.png](https://help.activitytimeline.com/__attachments/a_b3f5cf3cdc82f9272b4cd52d1024d1b48ffde7190ae7e6ff9dd79f21124b02fb/image-20220311-135619.png?cb=ace0df628598bcf89b76afb91f921651) ## Will ActivityTimeline work for people in different time zones? Yes, ActivityTimeline is configured to properly work for people in all time zones, regardless of the location of Jira Server and users' configuration. However, is also possible to configure different Timezone Shifts to allow larger flexibility in timezone management. If you need assistance with the timezone, please, contact our support team at [support@reliex.com](mailto:support@reliex.com). ## Can I integrate ActivityTimeline with Outlook or Google Calendar? Yes, it is possible to integrate ActivityTimeline with your Outlook, and Google Calendar. While Outlook integration works as an export only, Google Calendar integration supports both the export and import of events: [Integrating with Google Calendar - Export \& Import](https://help.activitytimeline.com/at/integrating-with-google-calendar-export-import.md) [Integrating with Outlook Calendar - Export \& Import](https://help.activitytimeline.com/at/integrating-with-outlook-calendar-export.md) ## I deleted the issue in Jira, but I can still see it in ActivityTimeline? First of all, you can try to press on '**Refresh** ' button to load the latest updates from Jira. If it did not help, you can go to *Configuration → Synchronization → Refresh issues → Detect \& Remove deleted issues:* First of all, you can try to press on '**Refresh** ' button to load the latest updates from Jira. If it did not help, you can go to *Configuration → Synchronization → Refresh issues → Detect \& Remove deleted issues:* ![1-20240912-122727.png](https://help.activitytimeline.com/__attachments/a_5c0f763e8b493661def6ee0952312c67002a97b21e0db490a738692d5b780cc5/1-20240912-122727.png?cb=eababd4ae3fa8251cc319ff1c77aca3f) In case the automatic 'Detect \& Remove Deleted Issues' function didn't work, you can still remove such issues manually in *Configuration → Issues → Maintenance:* ![2-20240912-122737.webp](https://help.activitytimeline.com/__attachments/a_222479aef546a3d22018fbeb8d5b608e8ed44651da29de70a00f7c1595c80b2c/2-20240912-122737.webp?cb=024581e5749b594d147f56fd1294e56f) ## How do I configure ActivityTimeline to use story points instead of hours? It is possible to use ActivityTimeline with story points instead of hours for estimation, however, for the system to properly calculate workload indicators and reports, story points must be converted into hours. This can be done on per project basis, meaning you can have different story point values in different projects. For this you need to configure a**conversion factor** in **Configuration → Projects → Click 'Manage'** near the project: ![3-20240912-122727.png](https://help.activitytimeline.com/__attachments/a_fc1ffa5496552ac793beb5bede66ff85f4f3d1e7fe91929e90c89d52f759bbec/3-20240912-122727.png?cb=8eb0d59d8530eb0385ac3055fdc4fcd1) * [Troubleshooting Page for Data Center Version](https://help.activitytimeline.com/at/troubleshooting-page-for-data-center-version.md) * [How to Fix 3rd party cookies (Invalid Session) error](https://help.activitytimeline.com/at/how-to-fix-3rd-party-cookies-invalid-session-error.md) * [How to setup 'Start/End dates for Jira Team-Managed Projects (formerly known as next-gen projects)' inside ActivityTimeline](https://help.activitytimeline.com/at/how-to-setup-start-end-dates-for-jira-team-managed.md) * [How to setup 'Story Points Estimate' field for Jira Team-Managed Projects (formerly known as next-gen projects) inside ActivityTimeline](https://help.activitytimeline.com/at/how-to-setup-story-points-estimate-field-for-jira.md) * [How to setup 'Original Estimate' and 'Time Tracking' fields for Jira Team-Managed (formerly known as next-gen) Projects inside ActivityTimeline](https://help.activitytimeline.com/at/how-to-setup-original-estimate-and-time-tracking.md) * [How to help support team to resolve your problem faster?](https://help.activitytimeline.com/at/how-to-help-support-team-to-resolve-your-problem-f.md) * [Increasing memory for ActivityTimeline Service on a large Jira Server/DC instance](https://help.activitytimeline.com/at/increasing-memory-for-activitytimeline-service-on-.md) * [ActivityTimeline with 3rd party SSO add-ons](https://help.activitytimeline.com/at/activitytimeline-with-3rd-party-sso-add-ons.md) * [ActivityTimeline on Jira Server/DC that is running on Java 11](https://help.activitytimeline.com/at/activitytimeline-on-jira-server-dc-that-is-running.md) * [ActivityTimeline app on Jira DC behind a Proxy server](https://help.activitytimeline.com/at/activitytimeline-app-on-jira-dc-behind-a-proxy-ser.md) * [Inter-node communication in ActivityTimeline for Jira Data Center](https://help.activitytimeline.com/at/inter-node-communication-in-activitytimeline-for-j.md) * [Jira DC with MS SQL Server database configured to use Integrated Security (Windows Authentication)](https://help.activitytimeline.com/at/jira-dc-with-ms-sql-server-database-configured-to-use-integrated-security-windows-authentication.md) * [Maintenance Guide of ActivityTimeline Server/DC](https://help.activitytimeline.com/at/maintenance-guide-of-activitytimeline-server-dc.md) --- language: "en" --- # FAQ – Legacy Version Setup This Q \& A section is related to the legacy version of ActivityTimeline (installable outside of Jira Server): [https://marketplace.atlassian.com/apps/1210888/activitytimeline-legacy-edition?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1210888/activitytimeline-legacy-edition?hosting=server&tab=overview) * [NGNIX Configuration](https://help.activitytimeline.com/at/ngnix-configuration.md) * [Database Switch](https://help.activitytimeline.com/at/database-switch.md) * [Restore Administrator Access](https://help.activitytimeline.com/at/restore-administrator-access.md) [Next Page](https://help.activitytimeline.com/llms-full.txt/1)