How can we help?

Download the installer for your platform from the PTIAS website, run it, then open the app and sign in with your PTIAS account. After sign-in, connect Jira using the OAuth flow (your browser will open for Atlassian). Updates are delivered through the same channel as your installer; follow any in-app prompts when a new version is available.

We love Jira! But No! - PTIAS Jira Companion is built by PTIAS - not By Atlassian. It works with your Atlassian Jira site using Atlassian-supported OAuth APIs; Atlassian is NOT the publisher of this app.

Jira access uses OAuth according to Atlassian's recommended patterns. You authorize the app in your browser with Atlassian; we do not ask for your Jira password inside our product for that step.

We do not store your Jira OAuth access or refresh tokens on PTIAS servers. Tokens stay on your device (for example in the operating system's secure storage) so that a compromise of our hosted infrastructure would not, by itself, hand an attacker your Jira API credentials.

We do not copy your Jira issue content to our servers as an application database. Issue summaries, descriptions, comments, attachments, worklogs, and similar data are exchanged between the desktop app and your organization's Jira. For account binding we only retain a small profile snapshot from OAuth (such as your Atlassian account ID, email, and display name). See the Privacy Policy for the full picture.

By default, closing the main window minimizes the app to the system tray (notification area) so reminders and background behavior can continue. Look for the PTIAS icon there to open the window again or quit completely.

In Preferences you can change what the window close (X) button does: for example, keep the default tray behavior, or close the main window and rely on the floating reminder widget instead. Pick the option that matches how you like to work.

Move the pointer over the main window (for example over the issue table or the top bar), hold Ctrl, and scroll the mouse wheel up or down. That adjusts the app font size in small steps (within the same limits as Preferences), applies it right away, and saves it for your next session.

The floating widget is a small on-screen companion (often near the edge of your screen) that supports time-tracking reminders. It can remind you when you have not logged time during the working hours and days you configured, and it works together with inactivity and over-logging reminders in Preferences.

If you dismiss or park the floater during a day when you still have not logged time in the allowed window, it can come back automatically to remind you to log time. Exact behavior depends on your reminder and working-hours settings.

Hover the floating widget and use your mouse wheel. The app follows this convention (also shown on the widget tooltip):

• Scroll — resize the widget.
• Shift + scroll — change color.
• Ctrl + scroll — change transparency (opacity).

You can also set color and opacity from Preferences if you prefer sliders and previews.

Yes. In Preferences, under behavior / reminder settings, you can choose the reminder sound (including built-in options or a custom file where supported), adjust volume, and tune movement (how far the icon shakes) and speed (how fast the shake cycles). These settings only affect your machine.

End users can adjust many reminder and behavior options in their own Preferences (for example inactivity delay, over-logging delay, lunch window, sounds, and floating widget options), subject to what your organization allows.

Customer Administrators can define organization policies from the web console. When a setting is enforced for your organization, the desktop app may show a lock icon next to that control and keep values within the range your admin chose.

The inactivity reminder helps when you have been idle for a while but may have forgotten to log time - it prompts you based on a delay you (or your admin) configure.

The over-logging reminder helps when a timer has been running a long time, so you do not accidentally leave work logged against the wrong issue - it reminds you after a configurable number of minutes.

Automatic actions let the app stop logging time for Jira items when you're going to lunch or at the end of the working day so those will not run when you're not really working on those Jira items.

In Preferences under the Behavior tab, find the Working Hours section. Set your usual lunch start and end time (within the same day and within reasonable limits shown in the app). You can optionally enable stopping all timers when lunch begins.

Lunch settings work together with your working hours and working days so reminders know when you expect to be logging time.

Open Preferences and choose a theme (light, dark, or other bundled styles). The app restyles the main window and dialogs to match; some themes are meant for long work sessions with reduced glare.

You must have set the reminder sound to Cat it out!, but you can change that by going to the Preferences window > Behavior tab and then select the default system sound or any custom sound file that you want to use.

Open Preferences and edit the list of Jira fields shown in the main window. Add fields you care about (for example Status, Assignee, or Time spent) and remove ones you do not need. When you save, the table refreshes to match; running timers are preserved where possible. You can also right-click a column header for a shortcut menu: add a column or field (opens Preferences), set text alignment for that column, remove that column, or remove similar or empty columns in one step.

Click a column header to sort by that column (toggle ascending and descending where supported). You can drag column headers to reorder columns.

For text alignment (left, center, right) per column, right-click the column header and choose Align Left, Align Center, or Align Right. You can also use the alignment controls in Preferences so numbers and labels line up the way you prefer.

That icon opens the Time tracking view for that specific issue: a popup window with a chart of time logged over the life of the Jira issue so you can compare the estimated with the spent time to see patterns without leaving the app.

My Worklog summarizes how much time you logged as worklogs: totals for today, yesterday, the last N days, and a custom date range (based on the issues currently loaded in your table). Use Show in table to add the Time spent field and narrow JQL to your worklogs; use export or copy actions if you need the numbers elsewhere.

Jira stores a worklog comment separately from issue comments. In Preferences you can enable a default worklog comment text that is applied when you log time (when that option is on).

You can also require or optionally prompt for a comment when you start a timer and/or when you stop it (optional vs mandatory modes). That helps teams that need every worklog entry to carry a short explanation.

Export to CSV writes the current table—headers and cell values—to a .csv file. The special Action column (start/stop controls) is omitted because it is not meaningful in a file. This format opens in Excel, Google Sheets, or any text editor.

Export with analysis (Excel) builds an .xlsx workbook. It includes your table data on a Data sheet plus extra columns derived from Jira relationships and time fields (for example parent and grand-parent keys, rollups, and percentage-style comparisons where configured). A second Parents sheet lists parent keys for hierarchy-style reporting. Use CSV for a simple dump; use Excel when you want the enriched analysis layout.

The Links Map is a graph view of issues from your current result set and how they link to each other. It helps you see clusters, dependencies, and orphan items at a glance. Open it from the toolbar when you have issues loaded; large tables may load a capped number of issues for performance (the button tooltip explains the limit when it applies).

Use the color picker at the top right to change the map background. Use the center map icon to re-center the view. Double-click the map background (empty area) to reset the view. Use the mouse wheel to zoom in and out. Click and drag on the map to pan. Right-click on the map to unselect items.

Hover a node to see its Jira summary in the UI.

Double-click a node to show only that issue's linked nodes and hide the rest of the graph (focus on that neighborhood).

Yes. In Preferences, open the User Interface tab and use Links map Jira fields. That list controls which issue fields the app loads and shows when you hover a node in the Links Map (the tooltip content). You can pick up to six fields; Summary must remain included. It is separate from Table's Jira fields, which only affects the main results table.

To link: click two nodes to select them, choose a link type, then use the Link button to create the link between the two items in Jira.

To unlink: click a link line (the edge between two issues) to select it, confirm you see the correct link type, then use the Un-Link button to remove it.

Use the eye icons to show or hide link types and issue types in the graph.

Type in the search field to highlight matching items (so you can spot them quickly without removing the rest of the graph).

Add child items creates new Jira issues that are children of the issue you started from (for example sub-tasks or other child types your Jira project allows). You choose the issue type and how many children to create.

Those children are linked through Jira's parent/child relationship, which then appears like any other link in the Links Map and in Jira's own hierarchy views. The dialog prevents invalid combinations that Jira would reject (such as a child type your project does not support).

You can optionally add extra is blocked by links between the new children (in creation order, which may differ from issue key numbering). Leave both options off if you only want the parent/child link and no chain between siblings:

• Link each item as blocked by the previous item in the list — builds a chain: each new issue is blocked only by the issue created immediately before it (the second depends on the first, the third on the second, and so on).
• Link each item as blocked by all previous items in the list (Great for GANTT!) — each new issue is blocked by every earlier child from that batch. Later items cannot start until all earlier steps finish, which stacks dependencies in a way that suits Gantt-style planning in Jira.

If both checkboxes are on, the all previous behavior is what runs; otherwise, with only "previous item" checked, you get the single-step chain.

Subscription and payment questions are handled in your account area after you sign in on the web. For invoice or access issues, email contact@ptias.com or use the Contact page.