Support

One person answers these, and answers them properly.

Documentation · Why it forecasts · Privacy and security · Support

Where to write

support@secondtiger.com — bug reports, questions, and feature requests all go to the same place.

What	Target
Acknowledgement	One business day (Korea Standard Time, UTC+9)
A diagnosis, or a question back	Three business days
Security reports	One business day — see privacy and security

What to include

The chart prints what it detected at the top, which is usually enough to find the problem without access to your site. Send:

• your site address, and the project or JQL you were looking at
• a screenshot of the whole chart, including the grey line at the top — it names the date field the app chose and why
• what you expected to see instead

Please do not send exported issue data. We do not need it, and we would rather not hold it.

Before you write — three things that are usually this

What you see	What it is
Bars are hollow outlines, not filled	Your issues have no start date set, so the created date stands in for it. The hollow outline is the app saying the start is estimated. Fill in start dates in Jira and the bars fill in too.
No forecast number, just a sentence about the sample	Not enough issues have finished recently to imply a pace. The app withholds the number rather than printing one it cannot stand behind.
History mode is missing, or says there is not enough record	The change log for these issues has too few entries to rewind — usually a young project, or one whose dates were set once and never moved.

What the app will not do

It will never write to your Jira site. If you want the app to move a date, that is not a missing feature — it is the product. Dates change in Jira only.

Documentation

The documentation covers how to read the chart, how the forecast is computed, and what the history mode can and cannot reconstruct.