Step-Free Scheduler for Jira
Email [email protected]. We answer within one business day, in English or German.
Written support only — there is no phone line and we do not take calls. That is a deliberate choice rather than an oversight: a written thread gives you the answer in a form you can forward, search and check, and it means the person who wrote the code answers you instead of a queue.
It saves a round trip, and most questions are answerable from it straight away:
Do not send screenshots containing anything confidential. We do not need them, and we would rather not hold them.
Jobs are dispatched hourly — a job set for 09:00 runs during the 09:00 hour. That is the finest interval the Forge platform offers and it is not something we can tighten. If a job did not run at all, open it and check the run history: every attempt is recorded there, successful or not.
Three things do that, and the job says which on screen: five failures in a row; the owner losing permission in the project; or the owner no longer being an active user. In every case, opening the job and saving it takes ownership and switches it back on — provided you can do the same thing by hand.
Not in this version, deliberately. A scheduled run is performed by the app rather than by you, and Atlassian gives an app no way to re-check your permissions while it runs. Confining each job to the one project you proved access to is what we do instead of asking you to make the app a Jira administrator.
Almost nothing. The app runs entirely inside your Atlassian site, and our logs carry counts and error codes, never your content — no page titles, no issue summaries, no names. That is good for your privacy and it does mean we sometimes have to ask you for detail we cannot look up ourselves. The privacy policy sets out exactly what is held and for how long.
Email [email protected] with enough detail to reproduce it. We will confirm receipt within one business day and tell you what we intend to do. Please give us a reasonable window to fix it before publishing.