-
Das interne Jira soll durch Issues auf GitHub ersetzt werden. Die Tickets müssen nach und nach übertragen werden.
-
When a release is created, the associated `release.yml` file should be updated with the created ticket so that we can then generate a status report for the release based on the information provided in…
-
-
To ensure we track tickets on a per-project basis we link them to epics in JIRA, and use whiteboard tags and/or metabugs in bugzilla.
When the bot files a JIRA ticket it would be nice if it got lin…
-
## Expected Behavior
Sometimes a single conventional commit can fix or resolve several work item tickets at once. In the case of Jira, for example, this might look like a commit message that in…
-
### Extension
https://www.raycast.com/raycast/jira
### Raycast Version
v1.83.2
### macOS Version
_No response_
### Description
Pressing on enter but it did not open jira task on d…
-
Here's the issue for tracking the update of v5.1 - v9
## Documentation
**Naming Convention**
- for subjects on Jira Tickets: "FMNH v9 [emodule] [tab/tool] [ColumnName]: [issue]"
> e.g.: "FMN…
-
## What
We have some old tickets in Jira for content style issues. They should all be in the GitHub backlog now.
## Why
We should have only one backlog so that people know where to go and can…
-
A `ContextProvider` is what allows you to type '@' and select from a dropdown of related items, potentially including GitHub Issues, local files, Jira Tickets, and more.
Docs for building a `ContextP…
-
Pull in all tickets from a specified [Jira Service Management](https://www.atlassian.com/software/jira/service-management) project.
Checkout the connector creation README here for more details on …