Comment on page
FAQs and troubleshooting
GitHub has added an additional layer of security for Organizations. You need to open up access in the Organization settings:
In Avion
In GitHub
Action | Result |
Update story | We will be update the issue where applicable, assuming that the story has been pushed or imported |
Delete story | We will close the issue |
Update release name | We will update the milestone name. Only applies to repo projects |
Archive release | Nothing will happen in GitHub |
Delete a release | The milestone and issues will be deleted in Github |
Update story state | We will update the project card column according to what is mapped in Avion |
Action | Result |
Delete issue | If the story has been pushed to GitHub, we will unsync the story and it will remain in Avion. Feel free to delete it from Avion if you don't need it |
Delete project card | If the story has been pushed to GitHub, we will unsync the story and it will remain in Avion. Feel free to delete it from Avion if you don't need it. The issue will remain in GitHub |
Close issue | Nothing will happen in Avion |
Delete milestone | If a release exists in Avion for the milestone, all synced stories will be moved to unplanned. The release will not be deleted, but will be unsynced (still in Avion). Only applies to repo projects |
Archive project card | Nothing will happen in Avion |
Close milestone | Nothing will happen in Avion. Only applies to repo projects |
Update issue | If the story has been pushed to GitHub, we will update the story in Avion |
Update issue size label | We will attempt to update the size in Avion |
Remove issue from milestone | We will move the story to the Unplanned release in Avion. Only applies to repo projects |
Change issue's milestone | We will attempt to update the story with the corresponding release in Avion. Only applies to repo projects |
Change project card's column | We will update the status of the story in Avion inline with your state mappings |
Update milestone name | We will attempt to update the corresponding release's name in Avion. Only applies to repo projects |
Transfer issue to another repo | We will unsync the issue, but the story will remain in Avion |
Delete repo | If you have synced to a repo-based project, we will remove the integration. If you have synced to an organisation-based project, we will update the list of repos in Avion and unsync any stories that came from that repo |
When synced to a repo-based project, you cannot use the same name for two Avion releases and push them, as GitHub has a clash restriction on milestone names.
Please note that we do not import closed issues or milestones. To import open issues, please ensure that there is a project card associated with the issue. To import open milestones, please ensure there is at least one issue in the milestone.
If you previously sync up Avion to GitHub, but want to add a new integration for another story map with an organization that is not getting recognised, you may need to grant privileges to Avion. You can do this by going to https://github.com/settings/applications when signed in as the user in question and granting the appropriate organization by clicking Grant:
This is supported in Avion. It can be a useful way to visualise different user journey setups. In particular, this works well with organization projects, as you can define different release plans and compare these plans beside each other.
- Ensure that you are an owner of the repo
- Ensure that you are an admin of the repo, if the repo is owned by an organization
- Ensure that you are an owner of the organization, if you want to sync with an organization project
- Ensure that there is a project with columns in the repo or organization
Yes, but only for repo-based projects.
Yes, but only for organization-based projects or ZenHub workspace integrations.
if you have optionally selected to sync Avion tags or releases to labels and are using the all-new project experience, labels should sync automatically, whichever tool you update them in. There is one exception. If you edit a label from the GitHub project item page, Avion will not update. This is a shortcoming with GitHub's webhooks. To avoid this data sync issue, update labels from the issue screen in GitHub, or from Avion.
Last modified 1yr ago