Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split fetching of dataset-level and subject/session-level query results into separate steps #265

Open
alyssadai opened this issue Jan 23, 2024 · 1 comment
Open

Split fetching of dataset-level and subject/session-level query results into separate steps #265

alyssadai opened this issue Jan 23, 2024 · 1 comment
Labels
feat:add The first minimal viable change that implements a new functionality. flag:detail needed Issue requires additional clarification before a decision can be made or it can be implemented. flag:discuss Flag issue that needs to be discussed before it can be implemented. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again type:feature Effort to deliver new features, feature changes & improvements

Comments

@alyssadai
Copy link
Contributor

No description provided.

@alyssadai alyssadai added feat:add The first minimal viable change that implements a new functionality. type:feature Effort to deliver new features, feature changes & improvements flag:discuss Flag issue that needs to be discussed before it can be implemented. flag:schedule Flag issue that should go on the roadmap or backlog. labels Jan 23, 2024
@rmanaem rmanaem removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Jan 31, 2024
@alyssadai alyssadai added the flag:schedule Flag issue that should go on the roadmap or backlog. label Apr 15, 2024
@surchs surchs added the flag:detail needed Issue requires additional clarification before a decision can be made or it can be implemented. label Apr 24, 2024
@rmanaem rmanaem removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Apr 29, 2024
@github-actions GitHub Actions
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feat:add The first minimal viable change that implements a new functionality. flag:detail needed Issue requires additional clarification before a decision can be made or it can be implemented. flag:discuss Flag issue that needs to be discussed before it can be implemented. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again type:feature Effort to deliver new features, feature changes & improvements
Projects
Neurobagel
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@surchs @alyssadai @rmanaem