You can use the ticket page to check the status of the work in progress as developers update the status of PRs internally. Tickets automatically change status based on PR activity. If you have multiple tickets, you can view the status of all tickets at a glance on the Instance homepage.
On selected plans, your project manager will also notify you about important events and keep you updated via Slack.
Discussion and clarification
Sometimes, our developers will need to clarify something about the ticket. They will do this by commenting on the PR and are able to tag you in the comment, respond with images, and more.
As mentioned during Instance setup, there should be a dedicated person from your organization managing each instance in order to get the most out of GitStart. Without them, PRs may stall, and, worse, we may not be able to complete the work on time or to the level of quality you expect.
See the next section for more information on PR reviews and change requests.
Scope change is defined as any change in ticket scope from the original description when it was first assigned to GitStart. Scope changes can be introduced by either party, and they can be either positive (adding more items or functionality) or negative (removing them).
We try to be reasonable about scope changes, but we also need to be fair to our developers. We will not accept scope changes that are too large or too frequent.
If it looks like the ticket scope is changing beyond what would be considered a minor change in a short PR review cycle, you must create a new ticket. This keeps disruption to a minimum and ensures we can track the scope change and changing criteria.
If it’s important to keep the same ticket, you can create a new pull request under the same ticket to fix the issue and update the PR and ticket cost accordingly. Please reach out to your project manager or email@example.com if you need help with this.