Jira Assistant began as a simple utility in 2016 for quickly adding worklog and pulling reports from Jira. Its motive is not to generate revenue. However, due to browser updates and other factors, it requires considerable effort to maintain the stability of the tool. Hence contributions from users in any form are welcome.

Jira Assistant is absolutely free and no PRO version is available as of date. However we try to provide support for blocking issues ASAP. Most of the blocking issues would be resolved within the weekend of current week.

JA is an open-source project where the source code is available on GitHub. Any developers are more than welcome to raise a PR for a bug fix or for a new feature. Guidelines for development are available under DEVELOPER menu.

Yes, JA works with both cloud and data center version of Jira. But it supports OAuth based authentication only with the cloud version. If you want OAuth to be supported in your data center version of Jira, please contact the developer.

If you want a Web, Mobile, Desktop or Browser extension to be developed and would like to pay for it, you can contact the developer through mail with the detailed requirement and can discuss further.

Jira Assistant pulls the data from Jira by calling the API exposed by Jira. Sometimes due to indexing issues, Jira API doesn't return some worklog, issues, comments, etc.,. If you face such issues, then I would suggest to check with your Jira admin and see if indexing in Jira is optimal. Most of the times, re-indexing Jira solves this issue of missing data in JA. This is not really an issue with this tool, but in Jira's API.

Jira Assistant is a free tool and is developed and maintained by a single developer. Due to the huge volume of support incidents and other priorities, it may not be always feasible for the developer to respond on timely basis. While contacting the developer, always provide exact information about the issue you are facing along with required screenshots / console errors if any. Unfortunately, not all issues are resolved and sometimes may not be attended due to other priorities.

Currently JA does not support holidays and leave of absence/time-off configuration. Holiday API integration is already a feature being tracked as part of #26. Please have a look at that for more details and provide your comments.

Due to the way notifications are implemented currently, it is not possible to mark all the notifications as read. If you open a Jira ticket, all the notifications related to that ticket is automatically not pulled next time. That way, only option to not show notification next time is to open individual tickets. There could be some better options in future and until then please bear with me.

With chrome, Jira Assistant is supported only for Chrome version above 102.x. So if you are using a old version of chrome, You are requested to upgrade to latest version of chrome and enjoy latest security updates provided by chrome along with updated version of Jira Assistant.

While importing issues, you can provide comma separated values for parent or project column, that way you would be able to generate sub-task for multiple tickets or create same issues under multiple projects. But you cannot use both the features together. Multiple values are allowed only in parent or in project field.

On the worklog popup, the comments section is mandatory by default. You have an option to configure the number of how many characters has to be entered to consider it as a valid comment. To configure this, go to Settings > General > Worklog [Tab] and find the section "Min length for worklog comments" and edit the minimum characters required. Setting this to '0' would make it a non mandatory field.

By default, JA doesn't allow to add worklog on closed tickets. But you can configure this behavior, go to Setting > General > Worklog [Tab] and check the checkbox "Worklog for closed tickets". Enabling this would let you to add worklog on closed tickets. Note: This option would work only if Jira is configured to allow this behavior.

From calendar view you can easily copy worklogs by two different ways. One by right clicking on the event and click on the copy menu which will open worklog popup where you can provide date and time of target worklog. Second option is even quicker and easier, just press the Alt key and drag and drop the worklog where you want it to be copied.

You can change the list of tickets shown in the suggestion drop down by changing the JQL. To configure the JQL, go to Settings > Advanced page and find the JQL corresponding to "Ticket suggestions JQL" label. You cannot edit the default JQL as it is for reference only, but you can edit the instance specific JQL.

As of now, JA doesn't support adding worklog from some of the views under Calendar. This is already known and in future based on popularity it could be supported. But as of now it is kept as low priority.

To rename your dashboard, navigate to that dashboard and click on the name header label. There you can change both the name and the default icon of that dashboard.

You can change the list of tickets shown in My Open Tickets gadget by changing the JQL. To change the JQL, go to Settings > Advanced and find the JQL corresponding to "Open tickets JQL" label. You cannot edit the default JQL, but you can edit the instance specific JQL.

Yes, you can build a new gadget by building a report using Custom Reports or Report Builder module. Once you have built a report and have saved it, it would be available under add gadget popup from where you can add it to dashboard as a gadget.

Some levels of customizations are allowed for each gadgets. You can look at the corresponding gadget's settings by clicking on the wrench icon and JA Advanced settings for some options to customize the gadget. But most of the customizations you expect can be built using Custom reports/Report builder.

You can add a custom gadget to your dashboard by building a report using the Custom Reports or Report Builder module. Once the report is created, you can add it as a gadget from the add gadget popup on the dashboard.

Yes, you can switch between tabbed layout and grid layout for your dashboard. Click on the wrench icon from the top right corner of the dashboard and select the 'Show in tabs' menu to toggle between the two layouts.

Yes, you can rename or delete a dashboard. To rename, click on the name header label and edit it. To delete, click on the wrench icon from the top right corner and select the 'Delete dashboard' option. Please note that deletion is irreversible.

Yes, you can view gadgets in full screen mode. Click on the 'Expand' icon (fa fa-expand) present in the gadget to expand it and view it in full screen.

To set a dashboard as a quick view page, click on the icon from the top right corner of the dashboard and select 'Set as quick view' from the menu. The dashboard will then appear as a popover when clicking the JA icon.

Yes, you can rearrange the position of gadgets on the dashboard. In grid layout, simply drag and drop the gadgets by their header to change their order.

You can add tickets to the Bookmarks gadget by clicking on the plus icon (fa fa-plus). This will allow you to add multiple tickets to the list of bookmarked tickets.

As of JA v2.71, this is no longer an issue for Chrome users. JA can now be integrated with any Jira instance, without requiring this permission. It's important because JA doesn't store your credentials; it directly connects to Jira using your browser's established authentication.

Jira Assistant requires access to Jira in order to establish integration. It uses the authentication established by your browser for this purpose, so you don't need to provide additional credentials. This approach enhances security and simplifies the integration process.

When integrating with Jira, ensure you're logged in to Jira from your browser. Use the appropriate URL format, like http:// or https://. Provide the Jira base path, not page URLs. E.g., use https://jira.yourcompany.com, not https://jira.yourcompany.com/browse. Incorrect URLs can lead to network errors.

Most importantly, ensure you're logged into Jira from the same browser. If you still face the issue, click 'Grant permission' on the 401 page in JA. Sometimes, JA's access to Jira is revoked, causing this error. For more details, check GitHub issue #214.

Ensure you're logged in to Jira from the same browser. If authentication issues persist, contact the developer with a screenshot of the error or console details for assistance.

Ensure you're authenticated with Jira on the same browser window. If CORS issues arise, upgrade your browser. If the problem persists, contact the developer for further support. Unfortunately, the exact cause of the CORS issue is not reproducible.

Firefox Multi Account containers are rarely used with JA, but they generally work for most users. However, specific users might face compatibility issues. The root cause is unknown, making it difficult to fix. For more details, refer to GitHub issue #103.

Yes, Jira Assistant is available as a browser extension for popular web browsers such as Chrome, Firefox, Edge, and Opera. You can install and use it on any of these browsers to seamlessly integrate with your Jira instance.

Absolutely, Jira Assistant allows you to integrate with multiple Jira instances. After authenticating with Jira in your browser, you can easily switch between instances by clicking on the Jira domain name displayed in the extension's header. This feature provides seamless access to various Jira instances.

Expressions are basically JavaScript Code. You will get the current data in Field object in the expression. You would be able to use most of the inbuilt JavaScript functions as well in your expression. For example you can write Field.assignee.name, Field.summary, parseInt(Field.timespent), etc.. You can use the usual JavaScript Math class and other operators for calculations as well.

Charts component in report builder module uses chart.js component. So, you can refer the official website of chart.js on how to pass data and other properties. But as of now no samples or documentation is available to explain about it. I will try to put something together in the future if time permits. But as this is not a widely used feature, it is of low priority at this moment.

As of now one sample YouTube video is available on how to generate simple reports with report builder. But as of now no documentation is available to explain about it. I will try to put something together in the future if time permits. But as this is not a widely used feature, it is of low priority at this moment.

From any of the reports, the user list popup doesn't save the details persistently. If you permanently want to save the users, then go to Settings > User groups and save the user groups to persist them. So, while generating report, sometimes if you want to generate report for only few set of users/groups, you can safely remove other users from popup and generate report. Once you reload the report, you will still see the old set of users.

From any of the reports, the user list popup doesn't save the details persistently. So, if you don't want to generate the report for a specific user, then you can safely remove the user/group from the reports page. It will not get saved and so next time you reload the report, all the saved users/groups will be populated again. Hence no separate users/groups selection is required in any of the reports.

By default, Jira Assistant would use your local timezone while uploading the worklog. Hence if you have not configured Jira with your local timezone, then Jira would show worklog in different timezone. Hence it is always necessary for you to configure Jira with your local timezone.

Any worklog in Jira should be pulled by Jira Assistant. Ensure that you are providing appropriate query, User details, date range, etc.. If you are sure that filters you provided is accurate and still worklog is missing, then it is probably the issue with Indexing in Jira. If there are any recent updates or it has been sometimes long since last indexing in Jira has happened, then most probably re-indexing Jira would solve this issue. Contact your Jira admin about re-indexing.

In worklog report, click on the config icon from top right corner of the worklog report which would open a popup. This popup will contain a tab named JQL. Here you can add any additional filters you want.

No, currently there are no such features available and no plans to implement it in future as well. Browser extension are not meant for such background task processing and we cannot rely on extension to do it. There could be instances where it fails and could cause troubles.

As of now, there is no inbuilt feature available as such. However, you can work around it by using other fields in Jira. For example, you can add a label to all the issues for which billing is not necessary and in worklog report, you can add a JQL filter to not pull issues with those labels.

Yes, you can export the settings only by selecting user groups which would generate a .jab file. You can share this file with anyone to whom you want to share the groups with.

Jira Assistant doesn't store any sensitive information anywhere. It just stores the settings, Jira url, Jira profile details including mail id in browser cache. However, while using credential based authentication, JA has to store the credentials you provide as well within cache. Additionally it stores schema of Custom Report and Report Builder if you have created any. You can read more about it from Privacy Policy page.

Jira Assistant stores all your data in your browser local storage only. It does not send any of your information outside your browser. Additionally, no credentials or other sensitive information is stored anywhere. To know more about our privacy policy, please visit https://www.jiraassistant.com/privacy-policy

JA stores all your data in your browser local storage only and in an unencrypted format. However, it does not store or send any of your information outside your browser. Additionally no credentials or other sensitive information is stored anywhere. Hence there are no known security concerns about the stored data. To know more about what kind of data we store, please visit https://www.jiraassistant.com/privacy-policy

Go to Settings > General > General [Tab], you have the option to change the working days.

Worklog report, by default pulls the report in current users local timezone. If the users are working from a different timezone, then pulling worklog in local timezone would cause difference in date/time. To solve it, for individual users/groups you can add timezone settings from user groups. Setting appropriate time zone would solve the issue.

To show customized list of menus, go to Settings > General > Menu options [Tab]. Select 'Show menus' and then select all the list of pages to be shown in menu.

To directly open a page when clicking on JA icon, go to Settings > General > Menu options [Tab]. Select 'Auto launch' option and select the appropriate page to be loaded directly.

To show a quick view of dashboard first you should enable quick view. To enable quick view, go to Settings > General > Menu options [Tab]. Select 'Show quickview dashboard' option and select the appropriate dashboard to be shown as quickview.

Currently JA does not support syncing the settings anywhere. Though browser like chrome provide option to sync settings across reinstalls, it is not suitable for JA to use those sync feature. You can use Backup feature for now to export the settings. Refer issue #67 in github for more details.

Latest version of Jira Assistant support exporting settings and later after reinstall you can import it from Integrate screen. You can export or import it by clicking on the instance name from top right side of JA.

Unfortunately, JA is developed and maintained by a single developer and as of now no other support is available. Hence it becomes difficult for a single developer to allocate time of replying to chats or resolving a bug on time. Queries raised are prioritized and resolved based on the supporting details provided and severity of the query

JA Web would receive updates as and when the issue is fixed and has a quicker turn around. But when it comes to extensions/desktop apps, it takes more time due to the waiting time in queue and publish of the store. Due to this waiting time, there will not be frequent publishes unless there are major bug fixes/features.

Some times their could be fixes specific to a browser or their could be very minor feature additions. So in such cases not all browsers gets JA updates immediately. But after a month or two, it would get updated along with new additions. Their could be one more reason where their was major refactoring in code which could have some negative impacts. In such cases also updates are first published to one browser for testing.

Chrome extension is updated on phased basis to avoid any breaking changes impacting all users. So it is pushed to a specific percentage of users and slowly pushed to other users over a time period. Hence you can either wait till it happens automatically or just go to "chrome://extensions" page and click update to immediately update your extension.

You can request for any new features by raising a ticket in GitHub with detailed description. Depending on available bandwidth, we would prioritize. If you are badly in need of a feature and if you are willing to make a one-time contribution for it, then after raising the ticket, you can contact the developer through mail. We can discuss further on it.

As of now, Jira Assistant works better with Chrome, Firefox, Edge and Opera. But few users use it with other browsers with minimal issues/work around's. With Vivaldi it is known to work well, but is not officially supported at this point. Additionally this can also be installed as an App within Jira cloud and let all your employee's use it.

Being a single developer, it is very difficult for us to getting into calls with individual users. So, we would suggest you to raise a support ticket with required details in Git Hub. Alternatively, if it is a question, discussions under GitHub can be used to ask your question.

Their are no specific interval on when the release would happen. Usually it would happen on weekends. But if their are major issue fixes, then it can happen on any day. Usually for planned feature releases, you would see the notification in JA with expected date of publish.

Mostly it depends on the availability of the developer and how soon you need it. Also if a feature is required within Jira Assistant, then it has to be generic and usable by all the users. Enhancements/requests which are useful only to specific users are generally not addressed.

Jira Assistant is a open source free software for both Personal and Official use. The source code is available in GitHub. You can even customize the code for use within your company and use it. If you are expecting for any specific use case, please contact the developer.

JA Web was primarily introduced to support BETA testing by users and to provide quicker fixes in case of major bugs. The Web version allows for immediate deployment of builds without waiting periods, giving users access to the next version of JA every day. Additionally, those who cannot install the app can still use JA Web through OAuth integration with Jira.

Currently, the sprint report does not work in JA Web OAuth integration due to a limitation in OAuth support for this specific API. This limitation will be addressed in the upcoming weeks as other priority tasks are completed.

JA Web was primarily introduced to support BETA testing by users and to provide quicker fixes in case of major bugs. Since builds are published whenever there are changes, some changes might not be fully tested, resulting in short-term bugs that will be resolved in subsequent builds.

Yes, JA Web is already available and hosted using GitHub Pages. If you prefer to host it within your data center, it can be done with minimal code changes based on how JA integrates with your Jira instance.

Similar to the extension, JA Web stores its data in your browser cache. JA Web is a static site hosted on GitHub, and it does not use server storage or cloud-based data storage.

You can easily switch between JA Web and the Extension anytime. To switch, click on 'Web' in the top right corner of the page. In case JA Web crashes and you can't switch back, you can go to the extension options page. For Chrome, right-click the JA icon and click 'Options', and for Firefox, go to 'Manage Extension' -> 'Options' tab.

JA Web can be used either as a standalone app or integrated with the extension. When integrated, all settings remain stored in the extension. The Web version communicates with the extension and displays the stored data.

JA Web offers a range of functionalities similar to the extension version, including creating dashboards, managing gadgets, generating reports, and integrating with Jira. You can also enjoy the benefits of custom dashboards, gadgets, and other key features in the Web version.

JA Web is designed to be compatible with most modern web browsers, including Google Chrome, Mozilla Firefox, Microsoft Edge, and more. However, some specific functionalities might vary across different browsers.