Support

The app is in read-only mode, which happens when it is not licensed — for example after a trial ends or before a subscription is activated. Listing, search and dry run keep working; write jobs are refused both in the UI and on the server. Once the license is active in Apps → Manage apps, the buttons come back. (On a Forge development site there is no license at all, so the app is read-only there by design.)

Jobs run in the background on Atlassian in resumable chunks, so closing the tab is fine — reopen the app and check the Jobs tab. Each page is processed as "add the new label, then remove the old one", so a job that stops partway leaves pages either untouched or fully converted, never with labels lost. If a job shows failed (including enqueue_failed or abandoned after 7 days without progress), press Resume: it continues from where it stopped and skips what is already done. Rate limits (HTTP 429) are retried automatically.

Version 1 covers pages and blog posts (global labels). Attachment labels and space labels are not yet handled. The job runs with the permissions of the person who started it, so pages you cannot edit are not listed in the dry run and are not changed — ask a user with the right permissions to run the job, or run it again after permissions are fixed. Label names must be lower-case with no spaces or the characters : ; , . ? & [ ] ( ) # ^ * @ ! ' ".

No, it is not permanent. The app calls Confluence's normal delete, which moves the attachment to the space trash; it never purges. A space administrator can restore it — see Restoring attachments above. Before anything is deleted you get a dry run with the count, total size and largest files, and every job writes a log (trashed, already-gone, skipped:version-changed, skipped:moved, failed) you can review in the Jobs tab. If an attachment was re-uploaded or moved to another page after the scan, the app skips it rather than deleting a version it did not check.

Attachment Sweep is shown only to site administrators. If you are not a site admin, the entry does not appear. Also, everything the app does runs with your own permissions: attachments and pages in spaces you cannot view are never scanned or listed. Scanning and the deletion dry run work without a license; creating a delete job requires an active license.

The scan looks for references in page and blog-post bodies (both the classic storage format and the new editor's ADF), in attachment-list and gallery macros, and in page properties such as cover images. Attachments referenced from another page show as referenced by other page, cover images as cover picture, and neither is offered for deletion. Things that can still cause surprises: a space-limited scan does not detect references from other spaces — run a site-wide scan if in doubt; attachments newer than the minimum age (7 days by default) are never listed; and a scan result older than 24 hours must be re-run before you can delete from it. Enable "also read drafts" if references exist only in unpublished drafts. If you still see a wrong result, email us the attachment's page URL and file name.

Open the page and choose Set review policy from the page's "…" menu, or click the Review: not set item in the byline under the title. Pick a reviewer, then either a due date or a review interval in days (the interval sets the next date each time the page is marked reviewed), and save. The policy is stored as a content property on the page; the page body and page version are not touched. To mark a page reviewed, use Mark as reviewed in the byline dialog or in the banner shown on due and overdue pages — the due date moves to today plus the interval. Site administrators can assign, mark reviewed or clear policies on many pages at once from the app's dashboard (Apps menu → Page Review Reminders → Overview): select rows, choose the action, check the dry-run count and confirm. Setting or changing a policy requires an active license; viewing works without one.

The app does not send email itself. Once a day it scans the pages that have a policy; for each page that is due soon or overdue it posts a footer comment on that page that @mentions the reviewer (or the page owner, if no reviewer is set). Confluence then delivers its own notification for the mention — in the notification drawer (bell icon) and by email, according to your Confluence notification settings. So check the page's comments and the bell first. A page gets at most one reminder per 30 days, and the same due date is not mentioned twice unless the state changes (for example from due soon to overdue); after you mark the page reviewed, the next due date starts a new cycle. Confluence itself may not email mention notifications on a site still in its trial period, or for repeated mentions on the same page. Reminders are only posted when the license is active and notifications are enabled in Settings. Independently of comments, due and overdue pages show a banner at the top of the page, the byline reads Review due soon or Overdue, and your own due pages are listed under Pages to review on the Confluence Home feed.

The app keeps its own index of pages that carry a review policy, because Confluence's search cannot filter pages by that property. Every policy set through the app is added to the index automatically. Policies that were written directly through the REST API, or created before an app upgrade, are not — for those, a site administrator opens the dashboard's Settings tab and presses Rebuild index. This starts a reindex job (visible on the Jobs tab) that enumerates every page on the site and reads its review property, so it costs roughly one API point per page. On a large site it may hit the daily point budget (scanBudgetPoints in Settings, 5,000 by default) and stop with a "carried over" note; it then continues the next day automatically, or right away with Continue rebuilding. The daily scan waits until the rebuild has finished. Afterwards, press Scan now to refresh the Overview. Rebuilding does not require a license — it only writes the app's own storage. The Overview's Check index shows how many pages are indexed and when the index was last rebuilt.

Open the Apps menu → Field Sweep (Jira site administrators only) and press Scan on the Overview tab. One scan reads every custom field, every saved filter's JQL, every board's filter/quick filters/estimation field/rank field, and every dashboard's gadgets where their configuration is readable, then cross-references all of it against each custom field. Large sites are processed in resumable chunks in the background, so you can close the tab, come back later and press Reload on the Overview tab to see the latest result. The scan always runs with the permissions of the administrator who starts it, so saved filters owned by other users are included even when they are not shared (Jira lets an administrator list them), and dashboards are included when they are shared with you.

Field Sweep never deletes a field for good, and a scan only reads. The "Can clean up" count and list are a starting point for your own review. When you have checked a field, a Jira site administrator with a license can move it to Jira's trash from the app (Choose fields to move on the Overview, or Move to trash… on a row of the Fields tab). Before anything moves, a review window checks each field with Jira again. A moved field can be restored from the app's Moved to trash tab (no license needed) or from Jira's Deleted fields (Settings → Work items → Fields). Jira deletes a trashed field and its values for good after 60 days. You can also delete a field yourself in Jira, where moving to the trash is called Delete. A field is counted as "Can clean up" only when the scan found zero references (in filters, boards or dashboards, in the areas Field Sweep can read — see the next question), it is on no screen, no other field shares its name, and Jira's usage tracking shows no recent value change. That last part has three cases: a real last-used date older than your threshold (365 days by default); "no change on record", meaning Jira tracks the field but its value has never changed since Atlassian started tracking — this does count toward "Can clean up", and the app notes that values set before tracking began are not in the record, so check real issues before deleting; and "not tracked", which the app lists under "Fields Field Sweep could not judge" and never counts as "Can clean up". Locked (Jira-managed) fields are always excluded. Fields that share a name with another field, and results from a scan that could not check everything (for example, the field-name index used to resolve JQL couldn't be fetched), are listed under "To review" rather than guessed at.

No — and Field Sweep would rather say what it did not read than quietly show zero. The last row of the Overview's checks, "What this scan did not read", lists the ranges a scan does not cover rather than folding them into the reference count: automation rules (Atlassian's Automation Rule Management API explicitly refuses Forge and OAuth2 apps), workflow conditions, validators and post-functions (not covered in this version), dashboards that are not shared with the scanning administrator (Jira's dashboard API never returns another user's unshared dashboard, even to an admin), and swimlanes and card-layout configuration (there is no public API for it). If a particular gadget's configuration could not be read for another reason (a transient error, an unrecognized third-party gadget), that is counted separately from gadgets that were read successfully but simply don't reference any field. Apart from workflows, these limits come from Jira's own permission model and API surface, and the app is built to say so rather than hide it.

CSV は、ヤマト運輸が公開している B2クラウドの取り込みレイアウト（CSV 仕様）に沿って作っています。ただし、実際の B2クラウドのアカウントでの取り込みの確認は、まだ行っていません。エラーが出たときは、画面のメッセージを添えて support@hullspark.com に送っていただければ調べます。

B2クラウドの利用には、ヤマト運輸との契約が必要です。クリックポストの利用条件は、日本郵便の案内で確認してください。このアプリが作るのは取り込み用の CSV で、配送の契約や送り状の発行は行いません。

出力前のチェックで、その注文は「出力できない」と出ます。Wix の注文の住所を直し、ページを開き直してください。

チェックに「宛名・住所・建物名が長く、途中で切れる」と出ます。その場で「半角にする」「書き直す」「切って出す」から選べます。直した値はこの出力にだけ使われ、Wix の注文は書き換わらず、保存もされません。ページを開き直すと元に戻ります。

代引きかどうかは、チェックの「確かめる」項目として出ます。自動では有効にならず、1 件ずつ確かめてから出力します。

文字コードは Shift_JIS が既定です。取り込めない文字は、チェックの「使えない文字」に出ます。

お届け先の個人情報は、このブラウザの中だけで処理し、サーバーに保存せず、外部にも送りません。ブラウザに残るのは、ご依頼主の情報・表示テーマ・レビュー依頼の既読だけです。Wix 側に残るのは、月ごとの出力件数と、「追跡番号を読み込む」で登録した発送（追跡番号と運送会社名）だけです。

月 30 件までの出力が無料です。数えるのは、その月に出力した注文の件数です。それを超えるには有料の Pro プランが要ります。価格は Wix App Market の掲載ページで確認できます。

はい。「追跡番号を読み込む」タブで、B2クラウドの発行済みデータ CSV を読み込み、注文番号と追跡番号の組を見比べたうえで、確認画面で「発送済みにする」を押すと、選んだ注文に発送（運送会社名「ヤマト運輸」と追跡番号）を登録します。注文のほかの内容は変えません。この機能にはアプリの権限「注文の管理」が必要です（既存のお客様は、Wix の「アプリを管理」でアプリを更新するときに承認します）。ストアの設定によっては、Wix が購入者に発送のお知らせメールを送ることがあり、アプリからは止められず、送られたメールは取り消せません。読み込んだファイルはブラウザの中だけで扱い、保存も Wix 以外への送信もしません。

在庫切れと残りわずかの通知は、スマホとダッシュボードのベルに届きます。基準を超えて戻ったときの通知は、ベルにだけ静かに 1 行出ます。通知の種類ごとにオン・オフでき、テスト通知で見え方を確かめられます。毎朝 8:00 に、在庫切れと残りわずかの商品を 1 通にまとめて知らせます（どちらもない日は送りません）。メールは送りません。

読みません。読み込むのは商品・カテゴリー・在庫だけで、お客様の情報や注文は読まず、外部のサーバーにも送りません。保存したデータはボタン 1 つで全削除できます。

日本語と英語の画面に対応しています。ライトとダークも選べます。

「基準 5 でチェックを始める」で、全商品に 1 つの基準を決められます（新しい商品も対象）。商品やバリエーション（サイズ・色）だけ別の基準にするときは、アプリ内の一覧から商品を検索して選びます。

Wix Stores の商品の在庫を読みます。動作を確かめたのは Wix ストアのカタログ V3 です。V1 のストアは未確認です。

無料プラン（Basic）でも、見張る商品の数は無制限です。通知、毎朝のまとめ、発注メモが使えます。Pro は月 $2.99（Wix App Market ではお使いの通貨で表示されます）で、14 日間無料で試せます。Pro では、カテゴリー全体に 1 つの基準を設定でき、毎週・毎月のまとめを好きな曜日・日・時刻に受け取れます。

残りわずかの商品を、仕入れ先ごとに並べたメモです。コピーも CSV 保存もできます。商品に「補充後の在庫数」を入れると、発注数（補充後の在庫数 − 今の在庫、0 未満にはなりません）も出ます。仕入れ先は名前だけで、住所や電話番号は要りません。

Press Ctrl+Shift+4 and drag over the part of the screen you need, or click New Capture… in the window. The capture opens in the editor; save it as a PNG with Export PNG….

Another app has probably registered the same combination. In the Hotkey box at the top of Markshot's window, click and press a different combination; Markshot tells you right away if the new one is also taken. Reset to default goes back to Ctrl+Shift+4. You can always use New Capture… in the window instead.

No. Markshot runs entirely on your PC and makes no network connections. Files are written only where you save them. See the privacy policy.

Email support@hullspark.com with your Windows version (Settings → System → About), the Markshot version shown in your Microsoft Store library, what you did and what you expected. A screenshot of the problem helps — blur anything private first.

No. CSV Splitter & Joiner runs entirely on your PC and makes no network connections. Your original files are not changed; the results are written to new files in the folder you choose. See the privacy policy.

Email support@hullspark.com with your Windows version (Settings → System → About), the app version shown in your Microsoft Store library, what you did and what you expected. Do not attach files that contain private data; a description of the file's shape (delimiter, encoding, rough size) is enough to start.

No. CSV Viewer & Extractor runs entirely on your PC and makes no network connections. Your original file is never changed; exports go to a new file and never overwrite an existing one. See the privacy policy.

Email support@hullspark.com with your Windows version (Settings → System → About), the app version shown in your Microsoft Store library, what you did and what you expected. Do not attach files that contain private data; a description of the file's shape (delimiter, encoding, rough size) is enough to start.

No. Excel Splitter by Hullspark runs entirely on your PC and makes no network connections. Excel is not started. Your original file is only read, never changed; the results are written to new files in the folder you choose and never overwrite an existing file. See the privacy policy.

With "By column value" and "Every N rows", each file holds only its own rows: other people's rows, other sheets you did not tick, hidden sheets and the author's name are not copied. ("By sheet" puts all rows of that sheet in each file.) But values that were calculated from other rows, from a sheet left out or from a name covering the whole table (running totals, ranks, totals on another sheet) stay as values. The result screen lists them under "Check before you hand them out", with a count and examples. The app can only spot values that come from formulas, so a total or text typed into a cell is not listed: open one output file and look before you send the files.

Email support@hullspark.com with your Windows version (Settings → System → About), the app version shown in your Microsoft Store library, what you did and what you expected. Do not attach files that contain private data; a description of the file's shape (number of sheets, rough size, what the split column holds) is enough to start.