Open the app a task's change runs in
Once a task's change merges, its page shows how far the change got on the way to production, and links to the app at that stage. Use it to try the change where it runs, without looking up the address. On an epic that built a hosted web app, the same button opens the app itself.
Who can do this: any member who can see the task. The button shows only once the change merged into a stage that has an address, or on an epic whose hosted app is set up or being set up. A task that changed no code has none.
- On the task board, select the task's title. Its page opens beside the board.
- Find the button marked ↗ in the header, at the top right of the page, before the state icon.
-
Read where the change is:
Button The change On dev Merged into the first stage, not released yet. Releasing Is in a release that is running now. Released Was released. Live Was released and deployed. On an epic: the app is up. Setting up On an epic: the app is still being set up. -
Hover the button to see the address it opens, such as Open the app: or Open dev: and the app's host name.
-
Select the button. The app opens at that stage's address in a new browser tab.
-
Try the change there. If it isn't what you asked for, go back to the task and add a comment, or start a new task for the fix.
The button moves on by itself as the change is released, so On dev becomes Releasing and then Released or Live. To release a change that waits on its first stage, see Release to production. Where each stage's address comes from is in Set a stage's deploy target.
Related
- Try a task's change in its slot — try the change before it merges.
- Read a task's result — the change a task delivered and what it cost.
- Task page — every item in the header.