The short version. Open the project's Standup tab, write your update from the issues you actually worked on, and post it whenever suits you. The team page shows who is blocked first, who hasn't posted, and a short summary of the day.
1. Write your update
In the project, open Standup and choose Write my update. There are three answers, whose wording a project admin can change: what you've done since your last update, what you're working on today, and your blockers.
- Suggestions. Under the first answer the app lists the issues in this project you updated or logged work on recently (the last 24 hours, 3 days or 7 days, as you choose), and under the second the issues assigned to you that are in progress. Tick one to link it. The suggestions come from Jira as you, so they only include what you can see.
- Blockers. Describe what's in your way, and add the keys of any blocking issues, for example
PTM-12, PTM-15. An update with a blocker is marked Blocked. - Limits. Each answer holds up to 1,000 characters and up to 15 linked issues.
You can edit or delete today's update until the day ends. Earlier days are read-only. When a day ends depends on the team's time zone and the hour a new day starts, set by an admin (by default 04:00, so a late evening update still counts for the day you worked).
2. The team page
- Blockers first. People who are blocked appear at the top, then everyone else in the order they posted.
- Linked issues show their title and status as you are allowed to see them in Jira. An issue you can't see is shown by its key only.
- Not posted yet lists the team members without an update today. The team is whoever posted in the last 14 days, or a fixed list chosen by an admin.
- History. The selector at the top opens any of the last 14 days, with how many updates and blockers each had.
3. The AI summary
Summarise the day turns the day's updates into a few sentences: progress, then blockers and who could unblock them, then risks.
- It stays in Atlassian. The summary is written by a model hosted by Atlassian (Forge LLMs). Nothing is sent outside your Atlassian cloud.
- What the model sees. The day's answers and issue keys, with people referred to as P1, P2 and so on. It never receives names, account IDs or issue titles; names are put back on your screen.
- Fresh, within limits. The summary is kept for the day. If updates change afterwards it is marked as out of date and can be refreshed up to three times a day. A site can generate up to 60 summaries a month.
- It's a summary, not the record. AI can misread an update; the updates themselves are what the team wrote.
A project admin can turn the summary off in the settings.
4. Settings
In Project settings (or Space settings) → Standup, project admins and Jira admins can set:
| Setting | What it does |
|---|---|
| Time zone and new-day hour | When one standup day ends and the next begins. |
| Questions | The wording of the three answers. The third is always treated as blockers. |
| Team | Whoever posted in the last 14 days, or a fixed list of people. Used for "Not posted yet". |
| AI summary | On or off for the project. |
| Keeping updates | Updates and summaries are deleted after 30 to 730 days (90 by default). |
5. Who can do what
| Who | What |
|---|---|
| Anyone who can browse the project | Read the team page and its history, post and edit their own update, ask for the summary. |
| Project admins and Jira admins | Change the settings. |
| Nobody | Write or delete someone else's update. |
Posting and summaries need an active licence; past updates stay readable without one.
6. Support
Support is handled by the developer who builds the app, in English and Spanish, Monday to Friday, 09:00–18:00 Central European Time, excluding Spanish public holidays.
Raise a request on the support portal, or email soporte@vantelia.es. Please don't include the text of updates in support requests.