Sub-task Field Inheritor for Jira: copy parent fields to sub-tasks

Sub-task Field Inheritor copies the fields a Jira administrator chooses from a parent issue to its sub-tasks. It runs inside the cloud product and sends nothing outside it.

日本語のページ

Free for up to 10 users; see Marketplace for tiers. For Jira Cloud. Runs entirely inside it.

What it does

Sub-task Field Inheritor copies the fields you choose from a parent issue to its sub-tasks, so nobody has to fill them in by hand. A Jira administrator picks the fields for each project. The app then copies them when a sub-task is created and when a chosen field changes on the parent. You can also apply the settings once to the sub-tasks that already exist, and undo that run.

Where to find it

It is an administration page in Jira, named Sub-task Field Inheritor. Only Jira administrators can open it; other people see a notice saying so.

Use it, step by step

  1. Open Sub-task Field Inheritor and choose a Project.
  2. Under Fields to copy from parent to sub-tasks, tick the fields to copy. Only ticked fields are read or written. For each one, choose how it is written (see Settings below).
  3. Under When to copy, tick When a sub-task is created, When a selected field changes on the parent, or both. On a parent change, only the field that changed is copied.
  4. Press Save. From then on, new sub-tasks and parent changes in that project are copied. Jira can deliver events up to 3 minutes late.
  5. To fill sub-tasks that already exist, press Count what would change. The result shows how many sub-tasks would change. Then press Apply now and confirm. It runs in the background and shows its progress. You can leave the page.
  6. To undo that run, press Undo last run and confirm. A field that someone has changed since the run is left as it is.
  7. The Activity log at the bottom shows the last 50 changes: time, source, parent, sub-task, fields and result.

Settings

Fields you can choose. Fix versions, Components, Labels, Due date, Priority and Assignee, plus custom fields of these types: text field, text area, number, date picker, select list, radio buttons, multi-select, checkboxes, user picker, multi user picker and labels. Other custom field types are listed as Not supported and are not copied.

Write mode, per field. For single-value fields: Follow the parent (the default) copies the new value when the sub-task is empty or still holds the parent's previous value, keeps a value someone set on the sub-task, and never clears the sub-task when the parent becomes empty. Only when the sub-task is empty copies only into an empty field. Replace with the parent value always overwrites, and clears the sub-task when the parent's field is empty. For multi-value fields: Add parent values (the default) adds the parent's values and keeps the sub-task's own; Replace makes the sub-task hold exactly the parent's values. Priority always has a value, so its default is Replace.

When a sub-task is created, and with Apply now, the parent's previous value is not known, so Follow copies only into an empty field.

Limits

  • Up to 25 fields per project.
  • It copies from a parent to its sub-tasks only, not the other way and not to other issue types.
  • Images and attachments inside long-text fields are not copied.
  • A field that is not on a sub-task's screen is skipped, and the log shows it.
  • An update to a sub-task never starts another copy, and a field is not written when the sub-task already has the same value.
  • Updates are sent without notification emails when Jira allows it. When Jira refuses, the emails are sent and the app tells you how many.
  • Undo covers the last Apply now run only, and records up to 200 sub-tasks. If a run was larger, the app says only the first 200 were recorded.
  • Large changes run in the background in batches, within Jira's write-rate limits, so they can take a while.

Licensing and price

Free for up to 10 users; see Marketplace for tiers. Without an active license you can view the settings, but saving and Apply now need an active license.

Data and privacy

The app stores the following in app storage on your site, per project: the settings, an activity log of the last 50 changes (issue keys, field IDs and results, not field values), the progress of a running job, and the record needed for Undo. The Undo record holds the previous and new values of the fields of up to 200 sub-tasks from the last Apply now run, so it can contain account IDs of users, such as an assignee. Each week the app reports those stored account IDs to the platform personal-data service, and removes the entries of closed accounts. It runs inside the cloud product and sends no data outside it. Uninstalling removes the data. See the Privacy page for Hullspark's policy.

Support

Write to support@hullspark.com or use the Support page. Include the project key, the issue keys and what you saw. Do not send issue content.