The Create a new Task event is triggered within GitScrum when a user creates a new task within a project. Tasks represent individual units of work that need to be completed as part of a project, helping teams organize and track their progress effectively.
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 task. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Create a Task event typically includes relevant information such as the task title, description, assignee, due date, task ID, project 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 task creation, assign responsibilities, and ensure a transparent workflow within GitScrum. Integrations can facilitate real-time updates, sync task 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 automate task notifications, the Create a Task webhook event in GitScrum empowers you to extend the capabilities of your project management processes. This event allows you to efficiently capture work items, track progress, and maintain a productive and organized workflow within your project team.
Raw Content
{
"uuid": "d6b07143-92dd-4084-8d81-92dee438100b",
"code": "#PROJC-1",
"effort": {
"title": "Large",
"effort": "1.00"
},
"type": {
"title": "MARKETING",
"color": "9900ff"
},
"timer": true,
"has_sprints": true,
"has_user_stories": true,
"workflow": {
"id": 5457,
"slug": "archived-64614fe26cc40",
"state": 1,
"title": "Archived",
"color": "f83a22"
},
"parent_id": null,
"image": null,
"labels": [],
"slug": "new-task",
"state": null,
"title": "new task",
"description": "",
"analyse": {
"risk": null
},
"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": [],
"features": [],
"completed_user": null,
"completed_date": [],
"start_date": [],
"due_date": [],
"created_at": {
"date_for_humans": "1 second ago",
"timezone": "2023-05-15 10:31:11",
"timestamp": 1684146671
},
"settings": {
"is_blocker": false,
"is_bug": false,
"is_draft": false,
"is_archived": true
},
"time_tracker": null,
"time_tracker_user": null,
"stats": {
"votes": 0,
"fields": 0,
"time_trackers": 0,
"comments": 0,
"checklists": 0,
"attachments": 0,
"subtasks": 0,
"videos": 0,
"checklist_percentage": 0
},
"company": {
"slug": "gitscrum",
"name": "GitScrum",
"logo": "https://gitscrum-storage-avatars.s3.amazonaws.com/37720bcf1e2f3340c54153d4e999c463f27c25c9.png",
"header_logo": "https://gitscrum-static.s3.amazonaws.com/img/gitscrum-black.png",
"header_color": "#882A2A",
"favicon": "https://gitscrum-storage-avatars.s3.amazonaws.com/9575b6c36682f58fd61e981ae843aac6e6e34263.png",
"owner": {
"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"
}
},
"project": {
"slug": "gitscrum-project-demo",
"name": "GitScrum Project Demo",
"logo": "https://gitscrum-storage-avatars.s3.amazonaws.com/37720bcf1e2f3340c54153d4e999c463f27c25c9.png",
"visibility": {
"is_private": false,
"title": "Public"
},
"recurring": {
"enabled": false,
"limit": 0
},
"owner": {
"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"
}
},
"board": {
"label": "Main Board",
"uuid": "main-board"
},
"sprint": {
"slug": null,
"title": null
},
"user_story": {
"slug": null,
"title": null
},
"rating": 0,
"has_recurring": false,
"is_favorite": false
}The Update Task event is triggered within GitScrum when a user modifies an existing task within a project. Tasks represent individual units of work that need to be completed as part of a project, and updating them helps teams manage changes, track progress, and ensure accurate project information.
When this event occurs, GitScrum generates a webhook notification, allowing integrations and external services to be informed and take appropriate actions based on the updated task. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Update a Task event typically includes relevant information such as the task ID, updated task details (such as title, description, assignee, due date), project information, modification timestamp, 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 task changes, communicate updates, and maintain a transparent workflow within GitScrum. Integrations can facilitate real-time updates, synchronize task 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 task boards, or automate notifications related to task modifications, the Update a Task webhook event in GitScrum empowers you to extend the capabilities of your project management processes. This event allows you to adapt to evolving project requirements, maintain accurate task information, and ensure a productive and organized workflow within your project team.
Raw Content
{
"uuid": "d6b07143-92dd-4084-8d81-92dee438100b",
"code": "#PROJC-1",
"effort": {
"title": "Large",
"effort": "1.00"
},
"type": {
"title": "MARKETING",
"color": "9900ff"
},
"timer": true,
"has_sprints": true,
"has_user_stories": true,
"workflow": {
"id": 5457,
"slug": "archived-64614fe26cc40",
"state": 1,
"title": "Archived",
"color": "f83a22"
},
"parent_id": null,
"image": null,
"labels": [],
"slug": "new-task",
"state": null,
"title": "new task",
"description": "",
"analyse": {
"risk": null
},
"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": [],
"features": [],
"completed_user": null,
"completed_date": [],
"start_date": [],
"due_date": [],
"created_at": {
"date_for_humans": "1 second ago",
"timezone": "2023-05-15 10:31:11",
"timestamp": 1684146671
},
"settings": {
"is_blocker": false,
"is_bug": false,
"is_draft": false,
"is_archived": true
},
"time_tracker": null,
"time_tracker_user": null,
"stats": {
"votes": 0,
"fields": 0,
"time_trackers": 0,
"comments": 0,
"checklists": 0,
"attachments": 0,
"subtasks": 0,
"videos": 0,
"checklist_percentage": 0
},
"company": {
"slug": "gitscrum",
"name": "GitScrum",
"logo": "https://gitscrum-storage-avatars.s3.amazonaws.com/37720bcf1e2f3340c54153d4e999c463f27c25c9.png",
"header_logo": "https://gitscrum-static.s3.amazonaws.com/img/gitscrum-black.png",
"header_color": "#882A2A",
"favicon": "https://gitscrum-storage-avatars.s3.amazonaws.com/9575b6c36682f58fd61e981ae843aac6e6e34263.png",
"owner": {
"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"
}
},
"project": {
"slug": "gitscrum-project-demo",
"name": "GitScrum Project Demo",
"logo": "https://gitscrum-storage-avatars.s3.amazonaws.com/37720bcf1e2f3340c54153d4e999c463f27c25c9.png",
"visibility": {
"is_private": false,
"title": "Public"
},
"recurring": {
"enabled": false,
"limit": 0
},
"owner": {
"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"
}
},
"board": {
"label": "Main Board",
"uuid": "main-board"
},
"sprint": {
"slug": null,
"title": null
},
"user_story": {
"slug": null,
"title": null
},
"rating": 0,
"has_recurring": false,
"is_favorite": false
}The Move a Task to Another Workflow Column event is triggered within GitScrum when a user relocates a task from one workflow column to another. Workflow columns represent different stages or phases of a project, providing a visual representation of the progress and status of tasks.
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 task movement. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Move a Task to Another Workflow Column event typically includes relevant information such as the task ID, source column, destination column, project details, movement timestamp, 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 track task progress, visualize workflow changes, and maintain a transparent workflow within GitScrum. Integrations can facilitate real-time updates, synchronize task 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 task boards, or automate notifications related to task movements, the Move a Task to Another Workflow Column webhook event in GitScrum empowers you to extend the capabilities of your project management processes. This event allows you to visualize task progression, optimize project tracking, and ensure a productive and organized workflow within your project team.
Raw Content
{
"task": {
"uuid": "d6b07143-92dd-4084-8d81-92dee438100b"
},
"workflow": {
"id": 5456,
"title": "Done",
"color": "#16a765"
}
}The Assign User to Task event is triggered within GitScrum when a user assigns a specific team member to a task. Assigning users to tasks helps teams delegate responsibilities, track ownership, and ensure clear accountability for completing project work.
When this event occurs, GitScrum generates a webhook notification, allowing integrations and external services to be informed and take appropriate actions based on the task assignment. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Assign User to Task event typically includes relevant information such as the task ID, assigned user details, project information, assignment timestamp, 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 efficiently allocate work, ensure clarity on task ownership, and foster a collaborative environment within GitScrum. Integrations can facilitate real-time updates, synchronize task assignments with other tools, and enable a seamless flow of information between GitScrum and your software development ecosystem.
Whether you need to integrate with a team collaboration tool, update user calendars, or automate notifications related to task assignments, the Assign User to Task webhook event in GitScrum empowers you to extend the capabilities of your project management processes. This event allows you to streamline task allocation, track individual responsibilities, and maintain a productive and organized workflow within your project team.
Raw Content
{
"task": {
"uuid": "d6b07143-92dd-4084-8d81-92dee438100b"
},
"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"
}
}The Unassign User from Task event is triggered within GitScrum when a user removes the assignment of a team member from a task. Unassigning users from tasks helps teams reassign responsibilities, track ownership changes, and ensure clear accountability for completing project work.
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 unassignment. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Unassign User from Task event typically includes relevant information such as the task ID, unassigned user details, project information, unassignment timestamp, 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 efficiently manage changes in task ownership, reassign work as needed, and foster a collaborative environment within GitScrum. Integrations can facilitate real-time updates, synchronize task unassignments with other tools, and enable a seamless flow of information between GitScrum and your software development ecosystem.
Whether you need to integrate with a team collaboration tool, update user calendars, or automate notifications related to task unassignments, the Unassign User from Task webhook event in GitScrum empowers you to extend the capabilities of your project management processes. This event allows you to streamline task reassignment, track changes in responsibilities, and maintain a productive and organized workflow within your project team.
Raw Content
{
"task": {
"uuid": "d6b07143-92dd-4084-8d81-92dee438100b"
},
"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"
}
}The Delete a Task event is triggered within GitScrum when a user deletes a task from a project. Deleting a task removes it from the project and associated workflows, signaling its completion or irrelevance to the project's goals.
When this event occurs, GitScrum generates a webhook notification, allowing integrations and external services to be informed and take appropriate actions based on the deleted task. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Delete a Task event typically includes relevant information such as the task ID, project details, deletion timestamp, 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 task lifecycles, maintain project data integrity, and ensure a transparent workflow within GitScrum. Integrations can facilitate real-time updates, synchronize task deletions 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 reporting systems, or automate notifications related to task deletions, the Delete a Task webhook event in GitScrum empowers you to extend the capabilities of your project management processes. This event allows you to streamline task management, maintain accurate project records, and promote a productive and organized workflow within your project team.
Raw Content
{
"uuid": "337f7b6c-a270-4819-9f5a-accfcb7e61e1"
}The Move Task to Another Project event is triggered within GitScrum when a user transfers a task from one project to another. Moving tasks between projects allows teams to reorganize work, align tasks with different goals, or adjust project structures as needed.
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 task movement. This event enables seamless integration with various third-party applications and services, enhancing project management workflows.
The webhook payload associated with the Move Task to Another Project event typically includes relevant information such as the task ID, source project details, destination project details, movement timestamp, 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 efficiently reassign tasks, realign project structures, and ensure a transparent workflow within GitScrum. Integrations can facilitate real-time updates, synchronize task movements 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 task boards across projects, or automate notifications related to task movements, the Move Task to Another Project webhook event in GitScrum empowers you to extend the capabilities of your project management processes. This event allows you to adapt project structures, track task reassignments, and maintain a productive and organized workflow within your project team.
Raw Content
{
"uuid": "d6b07143-92dd-4084-8d81-92dee438100b",
"project": {
"slug": "1-my-event",
"name": "1 my event"
}
}