The Create a New Sprint event is triggered within GitScrum when a user initiates the creation of a new sprint. Sprints are time-bound iterations within an Agile project that help teams organize and plan their work effectively, fostering collaboration and delivering incremental value.
When this event occurs, GitScrum sends out a webhook notification, allowing integrations and external services to be informed and take appropriate actions based on the newly created sprint. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Create a New Sprint event typically includes relevant information such as the sprint name, start and end dates, duration, team details, and other metadata. This data can be utilized to automatically update connected systems, notify team members, or trigger custom actions based on the specific requirements of your project management workflow.
By leveraging this webhook event, teams can streamline their sprint planning, track progress, and ensure timely delivery of project milestones within GitScrum. Integrations can facilitate real-time updates, sync sprint data with other tools, and enable a smooth flow of information between GitScrum and your software development ecosystem.
Whether you need to integrate with a project management tool, update a team's calendar, or automate sprint notifications, the Create a New Sprint webhook event in GitScrum empowers you to extend the capabilities of your Agile project management processes. This event allows you to optimize sprint planning, foster effective teamwork, and maintain a transparent and efficient workflow within your project team.
Raw Content
{
"id": 1,
"code": "#ST-1",
"slug": "gitscrum-01-64624e1b86e77",
"title": "GitScrum 01",
"color": null,
"timebox": "22-29 May 2023",
"date_start": "2023-05-22T00:00:00.000000Z",
"date_finish": "2023-05-29T00:00:00.000000Z",
"duration": "8 days",
"description": "Enhance the performance and responsiveness of the application to ensure smooth and efficient user interactions.",
"close_on_finish": false,
"company": {
"slug": "renato-marinho",
"name": "Renato Marinho"
},
"project": {
"slug": "gitscrum-project-demo",
"name": "GitScrum Project Demo"
},
"charts": {
"burndown_tasks": null,
"burndown_efforts": null
},
"stats": {
"story_points": 0,
"worked_hours": 0,
"total_tasks": 0,
"closed_tasks": 0,
"percentage": 0
},
"status": {
"slug": "sprint-standby",
"title": "Standby",
"color": "37c3ff",
"description": "standby a sprint"
},
"user": {
"name": "Renato Marinho de Carvalho",
"headline": "GitScrum Founder",
"username": "renato.marinho",
"avatar": "https://gitscrum-storage-avatars.s3.amazonaws.com/5467e2bdd31886166112fea09debe9f72aae06dd.png",
"location": "Lisbon",
"timezone_id": 37,
"timezone_name": "Etc/Greenwich",
"since": "October 2019"
},
"users": [],
"closed_at": {
"date_for_humans": "1 second ago",
"timezone": "2023-05-15 15:22:03",
"timestamp": 1684164123
},
"created_at": {
"date_for_humans": "1 second ago",
"timezone": "2023-05-15 15:22:03",
"timestamp": 1684164123
}
}The Update Sprint event is triggered within GitScrum when a user modifies an existing sprint, making changes to its properties, duration, or any other relevant details. Sprints are time-bound iterations within an Agile project that help teams plan, track, and deliver work efficiently.
When this event occurs, GitScrum generates a webhook notification, allowing integrations and external services to be notified and take appropriate actions based on the updated sprint. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Update a Sprint event typically includes relevant information such as the sprint ID, updated properties, modified dates, team details, and other metadata. This data can be utilized to automatically update connected systems, notify team members, or trigger custom actions based on the specific requirements of your project management workflow.
By leveraging this webhook event, teams can effectively manage changes to their sprints, ensure accurate planning, and keep all stakeholders informed within GitScrum. Integrations can facilitate real-time updates, sync sprint data with other tools, and enable a smooth flow of information between GitScrum and your software development ecosystem.
Whether you need to integrate with a project management tool, update team calendars, or automate notifications related to sprint updates, the Update a Sprint webhook event in GitScrum empowers you to extend the capabilities of your Agile project management processes. This event allows you to maintain accurate sprint information, adapt to changing project requirements, and ensure a transparent and efficient workflow within your project team.
Raw Content
{
"id": 1,
"code": "#ST-1",
"slug": "gitscrum-01-64624e1b86e77",
"title": "GitScrum 01",
"color": "#257e4a",
"timebox": "22-29 May 2023",
"date_start": "2023-05-22T00:00:00.000000Z",
"date_finish": "2023-05-29T00:00:00.000000Z",
"duration": "8 days",
"description": "Integrate a notification system to keep users informed about important updates and events within the platform.",
"close_on_finish": false,
"company": {
"slug": "renato-marinho",
"name": "Renato Marinho"
},
"project": {
"slug": "gitscrum-project-demo",
"name": "GitScrum Project Demo"
},
"charts": {
"burndown_tasks": null,
"burndown_efforts": null
},
"stats": {
"story_points": 0,
"worked_hours": 0,
"total_tasks": 0,
"closed_tasks": 0,
"percentage": 0
},
"status": {
"slug": "sprint-standby",
"title": "Standby",
"color": "37c3ff",
"description": "standby a sprint"
},
"user": {
"name": "Renato Marinho de Carvalho",
"headline": "GitScrum Founder",
"username": "renato.marinho",
"avatar": "https://gitscrum-storage-avatars.s3.amazonaws.com/5467e2bdd31886166112fea09debe9f72aae06dd.png",
"location": "Lisbon",
"timezone_id": 37,
"timezone_name": "Etc/Greenwich",
"since": "October 2019"
},
"users": [],
"closed_at": {
"date_for_humans": "1 minute ago",
"timezone": "2023-05-15 15:22:03",
"timestamp": 1684164123
},
"created_at": {
"date_for_humans": "1 minute ago",
"timezone": "2023-05-15 15:22:03",
"timestamp": 1684164123
}
}The Delete Sprint event is triggered within GitScrum when a user removes an existing sprint from their Agile project. Sprints are time-bound iterations that allow teams to plan, track, and deliver work effectively within specified timeframes.
When this event occurs, GitScrum generates a webhook notification, informing integrations and external services about the deleted sprint. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Delete a Sprint event typically contains relevant information such as the sprint ID, name, deletion timestamp, team details, and other metadata. This data can be utilized to automatically update connected systems, notify team members, or trigger custom actions based on your project management requirements.
By leveraging this webhook event, teams can maintain accurate project information, track progress, and ensure a streamlined workflow within GitScrum. Integrations can facilitate real-time updates, synchronize sprint data with other tools, and enable a seamless flow of information between GitScrum and your software development ecosystem.
Whether you need to integrate with a project management tool, update team calendars, or archive sprint data, the Delete a Sprint webhook event in GitScrum empowers you to extend the capabilities of your Agile project management processes. This event allows you to effectively manage sprint lifecycles, adapt to project changes, and maintain transparency and efficiency within your project team.
Raw Content
{
"uuid": "gitscrum-01-64624e1b86e77"
}