Troubleshooting and FAQ

JQL says my query could not be processed. Check the number is a whole number and the calendar name matches one on the Calendars tab, in double quotes. The functions work with date fields and the operators =, !=, <, <=, > and >=, not with in.

The fields are empty. Add them to the screen or work type. In team-managed projects, add them to the work type first. Values appear after the next refresh, or when you open the work item. Business days to due date is empty when there is no due date or the work item is resolved.

A value looks a day off. Dates are counted in the calendar’s time zone, not your own. Check the calendar’s time zone on the Calendars tab.

A holiday is missing or wrong. Check the country, state and region and the holiday types. Add a closure for missing days off, or untick a holiday your team works. Tell us at support@kayabyte.dev and we will look at the holiday data.

An automation step fails. Open the rule’s audit log. Daywise explains invalid input there, for example a date it cannot read or an unknown calendar. Dates need a time zone when they have a time, which smart values such as {{issue.created}} and {{now}} include.

Does Daywise change my SLAs, boards or timelines? No. Daywise adds its own JQL functions, fields, automation steps and panel. It does not change Jira Service Management SLA calendars, board settings or timelines.

Does Daywise send data outside Atlassian? No. It runs on Atlassian Forge and makes no calls outside Atlassian. See the privacy policy.

How much does the daily refresh do? It updates open work items and those resolved in the last three days, up to the limit on the Fields tab (20,000 by default). The first run after install fills every work item once, up to the same limit.