Skip to content

feat: Add scheduled campaigns support#1402

Merged
edgehog-app[bot] merged 4 commits intoedgehog-device-manager:mainfrom
OmarBrbutovic:timed_campaings
Apr 30, 2026
Merged

feat: Add scheduled campaigns support#1402
edgehog-app[bot] merged 4 commits intoedgehog-device-manager:mainfrom
OmarBrbutovic:timed_campaings

Conversation

@OmarBrbutovic
Copy link
Copy Markdown
Collaborator

@OmarBrbutovic OmarBrbutovic commented Apr 29, 2026

What this PR does / why we need it:

Add support for scheduled campaigns, allowing users to create campaigns that will be automatically launched at a specified future date and time.

Additional documentation e.g. usage docs, diagrams, reviewer notes, etc.:

Screenshots

Image 1 :
image

Image 2 :
image

Image 3:

image


Thanks for sending a pull request! If this is your first time, here are some tips for you:
  1. You can take a look at our developer guide for an introduction on Edgehog development!
  2. Make sure to read CONTRIBUTING.md and CODE_OF_CONDUCT.md
  3. If the PR is unfinished or you're actively working on it, mark it as draft

When fixing existing issues, use github's syntax to link your pull request to it

fixes #<issue number>

We also have a syntax to signal dependencies to other open pull requests

depends on #<pr number>
depends on https://github.com/...

In case of stacked PRs, you may add the PR number in the last commit's title instead:

gitGraph
    commit id: "Current master"
    branch feat1
    checkout feat1
    commit id: "feat: add something"
    commit id: "feat: add something else (#100)"
    branch feat2
    checkout feat2
    commit id: "refactor: do something"
    commit id: "fix: solve issue"
    commit id: "feat: add a feature (#101)"
    branch feat3
    checkout feat3
    commit id: "feat: feat without pr number"
Loading

@OmarBrbutovic OmarBrbutovic added frontend This issue is relative to the Edgehog Frontend backend This issue is relative to the Edgehog Backend labels Apr 29, 2026
Copy link
Copy Markdown
Collaborator

@lusergit lusergit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't even nitpick this

Image

Copy link
Copy Markdown
Contributor

@Dam-99 Dam-99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

Added Oban to the project by updating the configuration and creating
a migration for it. This will allow us to use Oban for background
job processing in our application.

Signed-off-by: Omar <omar.brbutovic@secomind.com>
Add support for scheduled campaigns, allowing users to create
campaigns that will be automatically launched at a specified
future date and time.

Signed-off-by: Omar <omar.brbutovic@secomind.com>
Added the ability to schedule campaigns in the future,
allowing users to set a specific date and time for campaign execution.

Signed-off-by: Omar <omar.brbutovic@secomind.com>
Expand documentation to explain how campaign scheduling works.

Signed-off-by: Omar <omar.brbutovic@secomind.com>
@lusergit
Copy link
Copy Markdown
Collaborator

/fast-forward 🥳

@edgehog-app edgehog-app Bot merged commit 34a6529 into edgehog-device-manager:main Apr 30, 2026
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend This issue is relative to the Edgehog Backend frontend This issue is relative to the Edgehog Frontend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants