Edit issue fields in the room

The room’s details panel shows the selected issue, and you change it right there without leaving the session. Changes go straight to where the issue lives: the card on its Laya board, Jira, or the session itself for a typed-in item.

What you can edit

The panel keeps SprintPoker’s own layout for every issue, the same sections and fields as in SprintPoker for Jira, and each field changes right where it is shown: click a value to change it. Edit Description opens the same editor a Laya board uses, with its AI tools. Click the status to change the status, and the work type icon beside the key to change the work type. There is no separate edit page to open.

For a Jira issue, Assignee offers the people the issue can be assigned to, and Reporter offers the people who can see the issue in Jira.

After a change made in the panel, the issue’s row in Session Issues shows the new summary, priority, assignee, labels and status, in every room that has the session open, and guests who may see descriptions see the new one. The estimate never changes this way: only Save & Next sets it.

A change shows the moment you save it, with Saving… beside the field and then Saved once the issue has it. If it can’t be saved, the field goes back to what the issue holds, says why after Didn’t save:, and opens your edit again so you can change it or try again.

A typed-in item lives only in the session, with a title and a description, and both can be edited in place: Edit Description opens the same editor a Laya board uses, with its AI tools.

Whose permissions apply

• A Jira issue that a board connected to laya.net holds is changed through that board, with the board’s own rules: the same Jira access the board uses, and only with permission to edit issues in its workspace.
• Any other Jira issue is changed in Jira as you, with your own Atlassian account, so Jira’s permissions decide. The editors on offer follow your own Jira edit screen, and when Jira refuses a change the room shows Jira’s own reason.
• With no Jira access of your own that works, a member of the workspace whose Jira connection reaches the session’s Jira site changes it through that connection, as on the workspace’s connected boards: only in the Jira projects that workspace mirrors, and only with permission to edit issues there. Anyone else links their Atlassian account first.
• A Laya card is changed as you, with your permissions on the card’s board: its fields need permission to edit the board’s issues, a comment needs permission to comment, and a sub-task card needs permission to create issues on the board. Without permission to edit the board’s issues, the panel shows the card read-only.
• A typed-in item can be changed by anyone seated in the session except guests, while the session runs.
• Your SprintPoker role doesn’t matter: observers can edit too. Your workspace role does: a Reader can’t change issues. Guests never edit.

Comments and child issues

Add comment... posts a plain-text comment as you: in Jira for a Jira issue, on the card for a Laya card (press M to start one). Add a child issue creates a child as you: for a Jira issue, a child issue in Jira one level down (for an epic you choose its type, with Task as the default); for a Laya card, a sub-task card on the card’s board with the same assignees. A sub-task can’t have children of its own.

Choose the fields the panel shows

In a session of Jira issues, moderators choose which fields the panel shows for each work type with Configure Work Type layout. The layout is saved for the board, shared with SprintPoker for Jira, and every room on the board picks it up. When a work type has no layout yet, moderators see You have not set the layout for this Work Type. with Use Default and Set Layout.

A Laya board’s layouts are set in SprintPoker settings, on the Workspace tab under Issue details layouts, by people who can change the board.