# Launching regular Jira background task with Forge

**URL:** <https://community.developer.atlassian.com/t/launching-regular-jira-background-task-with-forge/88696>\
**Category:** Forge\
**Tags:** jira-cloud, atlassian-connect, forge\
**Created:** [February 11, 2025, 10:41am UTC](https://community.developer.atlassian.com/t/launching-regular-jira-background-task-with-forge/88696 "2025-02-11T10:41:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![FabienLydoire](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/fabienlydoire/32/51218_2.png) [@FabienLydoire](https://community.developer.atlassian.com/u/FabienLydoire)\
**Post date:** [February 11, 2025, 1:30pm UTC](https://community.developer.atlassian.com/t/launching-regular-jira-background-task-with-forge/88696/2 "2025-02-11T13:30:36Z")

</div>

Maybe [Forge triggers](https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/) are what you are looking for.

> The `trigger` module invokes a function or calls a remote backend when a product event, app lifecycle event, or data security policy event is fired. For example, as the result of an issue being created in Jira.

You can listen to [Jira events](https://developer.atlassian.com/platform/forge/events-reference/jira/).

---

_[View the full topic](https://community.developer.atlassian.com/t/launching-regular-jira-background-task-with-forge/88696)._
