Myriastra Studio

User Guide — NudgeRoll for Jira

For Jira admins, project leads, assignees and PMs · Updated 29 October 2026

NudgeRoll asks the assignees of open Jira work items, by email, whether their work is ready for the release it is planned for. Each person answers with one press, such as Ready for review or Change due date, and NudgeRoll applies the answer to the work item in Jira as that person. Project leads see the answers on a board, and PMs see a view per version with a history for each work item and an .xlsx export.

NudgeRoll does not decide whether work is finished. A project lead or the reviewer confirms each work item that is marked ready for review.

1. How it works in one minute

  1. A Jira admin opens the NudgeRoll administration page, chooses the target projects by name and a time zone, presses Save, and then presses Start sending.
  2. Each target project's statuses are mapped to three groups: Working, In review and Done. A project admin does this in the project's NudgeRoll settings. To set up many projects at once, a Jira admin can use Set up by pattern on the administration page, and a project admin can copy one project's settings with Copy to other projects.
  3. Once an hour, from the morning hour in the chosen time zone, NudgeRoll looks at the open work items of the target projects. For each version, it works out how close the release date is.
  4. From the morning hour in the chosen time zone, each person gets at most one email a day that lists the work items they need to answer. Work items in a version more than a week from release are asked about once a week, and only when they need a look.
  5. The person presses a button in the email, such as Ready for review. A NudgeRoll page opens on the Jira site, and the person presses Submit. NudgeRoll applies the answer to the work item.
  6. The project lead or the reviewer confirms the work items that are ready for review.
  7. PMs open the PM view to see each version's work items, their states and the last answers, and to export them.

NudgeRoll has these screens:

ScreenWho uses itHow to open it
NudgeRoll administration pageJira adminsSettings (the gear icon), then Marketplace apps, then NudgeRoll under Apps on the left
NudgeRoll project settingsProject adminsIn the project: … next to the project name, then Space settings, then NudgeRoll under Apps on the left
NudgeRoll email formatEach person, for their own emailSettings (the gear icon), then General settings under Personal Jira settings, then NudgeRoll email format under Apps on the left; or the link at the end of a Full list email, which opens a NudgeRoll page with Use this format
NudgeRoll answerThe people asked in the emailA button in the email
NudgeRoll boardProject leads and reviewersThe link Open the {project} board in a project lead's email
NudgeRoll PM viewAnyone who can browse a target projectThe link Open the PM view for {project} in a project lead's email, or Open PM view in a PM's email

The answer page, the board and the PM view do not appear in Jira's menus. Open them from the links in the email, and bookmark the board or the PM view if you use them often.

2. Set up the app

You need to be a Jira admin.

  1. Open the NudgeRoll administration page: in Jira, select Settings (the gear icon) and choose Marketplace apps. A Manage apps page opens and says that app management has moved to Administration; you do not need to go there. In the menu on the left of that page, under Apps, select NudgeRoll. The page can take a few seconds to load.
  2. In Target projects, choose the projects NudgeRoll should ask about. The list shows each project as its name and key, such as IT Operations (KAN); type part of a name to narrow it. The chosen projects are listed below the field, each marked Set up or Not set up. Projects that are not set up get no email until their status mapping is saved (see the next section). If the list of projects cannot be loaded, the page says "Could not load the project list. Saved projects are shown by ID.", and the field cannot be changed until you reload the page and the list loads; on a site with more than 1,000 projects, it says "Only the first 1000 projects are listed."
  3. Check Time zone. On a site with no saved settings, it starts with your browser's time zone; after that it shows the saved one. Emails go out from the morning hour in this time zone. To change it, enter a time zone name such as Europe/London or Asia/Tokyo.
  4. Optionally, choose a Fallback recipient: type part of a name, press Search people, and choose from the results. The fallback recipient gets the project lead's part of the email when the project lead is no longer active, so that someone is told. The buttons in that part work only for project leads; to let the fallback recipient act on the work items, add them as a project lead in the project settings. Clear fallback recipient removes the choice.
  5. Press Save. You see "Saved".
  6. Set up the target projects: one at a time in each project's settings, or several at once with Set up by pattern, below Save on this page (see the next section).
  7. When the projects are set up, press Start sending at the bottom of the page. The screen shows "Started on …".

Press Save before Start sending. Nothing is sent until the settings are saved and sending has started. Start sending is recorded once, and the button is unavailable after you press it. When you open the page again later, it does not show whether sending has started, and the Start sending button can be pressed again. If sending has started, pressing it shows "Already started on …" with the original date; if it has not, pressing it starts sending.

3. Set up a project

You need to be an admin of the project. A project is not emailed until its status mapping is saved.

Open the project. Next to the project name, select … and choose Space settings. In the menu on the left, open Apps and select NudgeRoll.

Status mapping (default). Choose the statuses of the project for each of three groups:

GroupWhat it meansUsed when someone answers
WorkingThe work is in progressSend back moves the work item to the first status listed for this group
In reviewThe work is ready for someone to checkReady for review moves the work item to the first status listed for this group
DoneThe work is finishedConfirm done moves the work item to the first status listed for this group

Each group needs at least one status. A status in Working cannot also be in another group. In review and Done can share a status, for a workflow that has only a done status; then Ready for review already makes the work item done, and Confirm done only records the check.

The default mapping is used for work item types that have no setting of their own. Below it, you can set a different mapping for a work item type. The work item types are listed by name, such as Work item type: Task.

Below the mappings, NudgeRoll checks the project's workflow against a few existing work items, when the page opens and after Save. If an answer has no direct transition from a status, a warning names the work item type and the two statuses, and says that the button may not be applied. A line such as "28 combinations could not be checked (no work item in that status, or it could not be read)" means there was no work item to look at for those statuses; it is not an error.

Project leads and PMs. The Jira project lead receives the project lead's email. To add more project leads, find people by name with Search people and choose them under Additional project leads. Choose the PMs of the project under PM. If no PM is chosen, no PM email is sent.

Other.

Press Save. You see "Saved".

Copy to other projects. At the end of the project settings, Copy to other projects copies this project's saved settings to other projects: the status mapping with its settings for each work item type, the reviewer field and the days. The project leads and PMs of each project you copy to are kept. If you changed the status mapping, the reviewer field or the days and have not saved them, the page says "You changed the settings above. Save them first — Copy uses the saved settings." and you cannot copy until you press Save.

  1. Press Choose projects. The Projects field appears empty; open it to see the other projects you can manage.
  2. Choose the projects. Select all not set up chooses all the listed projects that are not set up yet. A project that is already set up is shown with "— set up, will be overwritten", and is copied to only if you choose it.
  3. Press Copy to 3 projects (with the number you chose). The page says how many projects will be copied to and how many of them will be overwritten. Press Confirm, or Cancel to go back.
  4. The page shows "Processed 3 of 3" while it works, and then one line for each project, such as "IT Operations: Saved".

Statuses are matched by name and by status category (To Do, In Progress, Done). A project that does not have a status of the mapping, or has it with a different category, is not changed, and its line names the status, such as "Status "In Review" is not in this project". If this project has settings for single work item types, a project without the same work item types is not changed either (team-managed projects have their own work item types). Lines that end with "you can retry", such as "Could not save — you can retry", and the line "The result is unknown — reopen this page to check" can be tried again with Retry with the same settings. Lines that give another reason, such as a missing status, are not retried; fix the cause and copy again.

Set up by pattern. Jira admins can set up many target projects at once on the administration page, under Set up by pattern. It uses the saved target projects; if you changed Target projects and have not saved, the page says "You changed the target projects. Save them first — this section uses the saved targets."

  1. Press Read statuses. The page shows "Read 20 of 45" while it works.
  2. The projects are grouped by their statuses: projects whose statuses have the same names and the same categories are in one group. Each group is headed by its number of projects and its statuses, such as "2 projects: Done · In Progress · In Review · To Do", and lists the projects under "Not set up" and "Already set up".
  3. In each group, choose the statuses for Working, In review and Done. The rules are the same as in the project settings: each group needs at least one status, and a status in Working cannot also be in another group.
  4. Projects that are already set up are not changed, unless you choose them in Also overwrite these set-up projects.
  5. Press Save to 2 projects (with the number of projects). The page says how many projects will be saved and how many of them will be overwritten. The mapping replaces the project's settings for single work item types; the project leads, PMs, reviewer field and days are kept. Press Confirm, or Cancel to go back.
  6. The page shows "Processed 2 of 2" while it works, and then one line for each project, such as "IT Operations (KAN): Saved". Lines that end with "you can retry" can be tried again with Retry with the same mapping. Lines that give another reason are not retried; fix the cause, or set the project up in its own settings.

Projects whose statuses could not be read are listed under Could not read, with the reason. Set them up in their own project settings.

4. The email

NudgeRoll sends one email a day at most to each person, through Jira's own notifications. The subject is "NudgeRoll: 3 items to check today", with the number of items. If there is nothing to ask a person, no email is sent.

Which work items are asked about. The open work items of the target projects, by the version in their Fix versions field:

Who gets which part. One person can hold several roles; they get one email with a part for each:

PartWhoWhat it holds
Assigned to youThe assignee of each work itemThe work items to answer, with Ready for review, Still working, Change due date and Unassign
As project leadProject leadsWork items that are unanswered, sent back, unassigned, with an assignee no longer active, not applied, whose email could not be sent, or ready for review. Each line has Confirm done and Send back, and the part has the link Open the {project} board
To reviewThe person in the reviewer field, unless they are also a project leadWork items ready for review, with Confirm done
PMPMsFor each version, the counts (total, done, open, needs a look, unanswered) and the open work items with their last answer, and Open PM view. The PM part has no answer buttons
Nothing left openPMsOnce, when the last open work item of a version is done. If the project uses issue security, it says nothing left open among the work items you and the app can see. Not sent for work items with no fix version

The number in the subject counts the work items, plus the PM versions and the versions with nothing left open.

In the parts for assignees, project leads and reviewers, each line of a work item gives its key, summary, status and due date (or No due date); a PM's lines give the key, summary, state and last answer. A line can carry a mark: Sent back, Assignee changed (with the previous answer when there was one), Could not be applied to Jira or May not have been applied — check the work item, the last two with a link Open work item.

Each email lists only work items that both the app and you can view. A list shows up to 100 work items; the rest are counted, and the email says "Only the first 100 items are listed. Check the rest in Jira."

5. Answer from the email

  1. Press a button next to the work item in the email. The NudgeRoll answer page opens on your Jira site as a full page, without Jira's top bar and menu on the left; the board and the PM view open the same way. It shows "Loading…" for a few seconds. Then, from the top, it shows "You opened this page from a NudgeRoll email. Nothing changes until you press Submit.", the work item's key and summary, its Status, the Action, for most actions a line on what Submit will do, and "Your answer is kept in the NudgeRoll answer log."
  2. For Change due date, choose the New due date from the calendar; the empty field says Select a date. The page does not show the current due date. If the date is after the release date of the work item's version, the page says "This date is after the release date. You can still submit it."
  3. Press Submit. After you choose a date, Submit stays unavailable for a moment while the page checks the date.

The Status line shows the status when the page opened. After Submit goes through, it shows the status of the work item again. If NudgeRoll cannot read it then, the line says Status when opened instead.

The first time you open a NudgeRoll screen, Atlassian may ask you to allow the app to access Jira on your behalf. Allow it to continue. The app uses that access to show work items with your own permissions and to apply your answers as you. On that first visit, the answer can take two presses: the permission, then Submit.

What each answer does:

ButtonWho can use itWhat happens in Jira
Ready for reviewThe assignee or a project leadMoves the work item to the first status of the In review group
Still workingThe assignee or a project leadNothing changes in Jira. NudgeRoll records the answer, and the work item no longer counts as not updated
Change due dateThe assignee or a project leadSets the work item's due date
UnassignThe assignee or a project leadRemoves the assignee. The project lead then sees the work item as unassigned
Confirm doneThe reviewer or a project leadMoves the work item to the first status of the Done group
Send backA project leadMoves the work item to the first status of the Working group. The assignee sees Sent back in the next email

After Submit, the page shows one of these:

NudgeRoll reads the work item again when the page opens and when you press Submit, and treats Jira's current value as correct. It uses only a direct transition from the current status; if the workflow has none, the page says "Could not be applied to Jira". If the page says "This project is waiting for setup", the project's status mapping has not been saved yet.

6. The project lead board

Project leads open the board with Open the {project} board in their email. A reviewer who is not a project lead sees only the work items they are asked to check; their email has no board link, so they open the board from its address, for example one a project lead shares.

The board lists the open work items of the project that NudgeRoll has asked about or that need action, in five sections, each with a count:

  1. Awaiting review: marked ready for review and waiting to be confirmed.
  2. Unanswered: asked and not answered yet.
  3. Needs action: unassigned, or the assignee is no longer active.
  4. Not applied, not confirmed, or delivery failed: an answer that Jira did not accept, an answer that may not have been applied, or an email that could not be sent.
  5. Answered.

Each work item is a card with its key and summary, its status, assignee, due date, reviewer and versions, and marks such as Sent back, Assignee changed, Self-review (the assignee is also the reviewer, or, when the reviewer field is empty, a project lead) or May not have been applied — check the work item. The top of the board can show PM not set, Status mapping needed, Version has no date or Past release date.

Each section shows its first 10 work items. Press Show 20 more (35 remaining) to see more; when fewer than 20 are left, the button shows that number. The count in the section heading is the full number, including the work items not shown yet.

Press an action on a card. The action opens in a window in front of the board, wherever the card is, with the work item key and the action as its title. It shows "Loading…" for a few seconds before Submit can be pressed. Check it, and press Submit, or Cancel (or Esc) to go back. After Submit, the window shows the result, such as "Applied to Jira", and the board behind it reloads; press Close to close the window (if Submit was refused, for example because the action is not allowed, the button still says Cancel). The board lists only open work items, so a work item you confirm as done leaves the board instead of moving to another section. The actions of a project lead depend on the section:

SectionActions
Awaiting reviewConfirm done, Send back, Change assignee
UnansweredReady for review, Still working, Change due date, Unassign, Change assignee
Needs actionChange assignee, Ready for review, Change due date
Not applied, not confirmed, or delivery failedReady for review, Still working, Change due date, Change assignee
AnsweredReady for review, Change due date, Change assignee

Change assignee is only on the board: find a person by name with Search people and choose the Assignee. A reviewer has Confirm done only, on work items awaiting review.

Several work items at once. Cards with Confirm done, Change assignee or Change due date have a check box. You can select up to 20 work items, all in one section. When 20 are selected, the other check boxes become unavailable and the board says "You can select up to 20 at a time." Selecting a card in another section starts a new selection there. Select all shown (up to 20), at the top and the bottom of each section that has a card with a check box, selects the cards that are shown. The board then shows how many are selected, Clear selection, and a button for each of those three actions that all the selected work items have. They appear next to Select all shown (up to 20), at the top and the bottom of the section, not next to the card you selected.

  1. Press the action, such as Change due date. A window opens with the action and the number of work items as its title, and lists the Work items.
  2. For Change due date, choose the New due date. For Change assignee, find a person with Search people and choose the Assignee.
  3. Press Submit. The window shows "5 of 10 processed" while it works, and then one line for each work item, such as "KAN-12: Applied to Jira". A line can also say "Not sure if applied — check the work item", "Not sent — you can retry" or "Already recorded — check the work item".
  4. If some work items can be tried again, Retry failed shows how many; press it to send them again. Press Close when you are done. When the work is finished, the board reloads and the selection is cleared.

7. The PM view, history and export

Anyone who can browse a target project can open its PM view, from Open the PM view for {project} in a project lead's email or Open PM view in a PM's email. These links are only in Full list emails. The view counts and lists only the work items you can see.

  1. Choose a Version. Released and archived versions are marked, and No version lists the work items with no fix version.
  2. The counts are shown as tiles: Needs a look, Unanswered, Open, Done (with how many are not confirmed, if any), Total and Self-review. Needs a look and Unanswered are highlighted when they are above 0. By status gives the count for each status.
  3. Open work items, with their number, lists each open work item as a card with its status, assignee, due date, state, how long it has been unanswered, why it needs a look (Overdue, Not updated, Assignee inactive, Unassigned) and the last answer. Use Previous and Next to page through.
  4. Press Show history on a work item to see its log. The history opens in a window in front of the view. It shows emails sent and failed, answers, actions of project leads, answers not applied, and changes made outside NudgeRoll to the status, assignee or due date. The most recent 500 entries are shown. Close closes it.

Export. At the bottom of the view, under Export, press Export xlsx. The file nudgeroll-pm-<project key>-<version ID>-<date>.xlsx has two sheets:

The export holds only each work item's last answer. The full history stays in the app's log and is shown with Show history.

If the version has more work items than one view or export can hold, the screen says it shows a partial list, and how many work items could not be shown. If the file would be too large, the screen says "The file is too large (limit: 3 MB)".

8. Choose your email format

Each person chooses the format of their own email:

There are two ways to switch:

9. Data retention and uninstalling

The log of a work item is kept for two years after its last entry, and is then deleted as a whole. There is no setting to change this period.

When the app is uninstalled, it stops, and its log and settings are no longer used. According to Atlassian's Forge documentation, the app's storage is then kept for 28 days and afterwards handled under Atlassian's own retention and disposal policy, so the data is not erased the instant you uninstall. The .xlsx export holds only the last answer for each work item, not the full answer log, so export before uninstalling if you need it. The administration page and the PM view show this notice: "If you uninstall the app, its answer log is deleted. The xlsx export holds only the last answer for each work item, so export first if you need that." The notice is short; the deletion follows the timing described above. What the app reads, writes and stores is described in the Privacy and Security Policy.

10. Stop emails for a project

To stop emails for a project, a Jira admin removes it from Target projects on the administration page and presses Save. At least one target project is needed. The project's answer page, board and PM view then stop working too, and say "This project is not one of the target projects". An email that Jira asked the app to retry can still go out in the next hourly run. This version has no setting to pause sending for the whole site; to stop it, uninstall the app, after exporting what you need.

If the app's license for your site is inactive, no email is sent and changes made outside NudgeRoll are not collected. The screens and the export still open, but answers and settings are paused: an action that would change something, such as Submit, Save or Start sending, shows "The NudgeRoll license for this site is inactive, so answers and settings are paused. Ask your site admin to renew the license." Sending resumes after the license is active again. The deletion of expired log entries continues while the license is inactive.

11. Limits worth knowing

12. Getting help

Email contact@myriastrastudio.com. Please do not send an exported workbook or the summaries of your work items; describe what you see on the screen instead, with the work item key. What the app reads, writes and stores is described in the Privacy and Security Policy.