Repository navigation
Conversation
GGraziadei
approved these changes
Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
Storm tracks work on GitHub Issues now (README was updated in #7936), but DEVELOPER.md still pointed people at JIRA.
I updated it to match current practice:
good first issuelabel instead of the old JIRA newbie/trivial filtersFixes #123), rather than prefixingSTORM-123:Docs only; no code changes.
What is the purpose of the change
Keep the developer docs in line with the GitHub Issues workflow.
How was the change tested
I read through the updated sections and checked that every JIRA workflow link in DEVELOPER.md is gone. I left historical STORM-XXXX citations in other files alone.
An AI assistant helped draft this change; I reviewed it and take responsibility for it.