#1 will be also my favorite.
Cheers Chris Von: Eric Bresie Gesendet: Samstag, 4. Dezember 2021 18:22 An: Netbeans Developer List Betreff: Re: Apache JIRA vs GitHub issues / discussions On Sat, Dec 4, 2021 at 10:18 AM Neil C Smith <[email protected]> wrote: > The emphasis in #1 should be to reduce the noise and raise the bar for > reporting issues, such that issues become a useful tool for release > management, rather than push everything into discussions. Otherwise > it may be a little too close to the chaos we have in JIRA now. > Maybe more in support of "option #2" improvements but... Can someone with the github power enable "auto links" from Github to JIRA (see below) to allow in github context reference to "NETBEANS-xxxx" to be automatically linked to the JIRA ticket? Would allowing visibility in the JIRA context of Github details also help reduce the headache? More details below...ignore if not interested.. From https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/ "When your GitHub or GitHub Enterprise account is linked to Jira Software, your team gets to see their branches, commit messages, pull requests, builds and deployments right in the context of the Jira Software issues they're working on. Read more in Integrating with development tools <https://confluence.atlassian.com/adminjiracloud/integrating-with-development-tools-776636216.html> ." From https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-development-tools/ "Workflow triggers Workflow triggers can help keep Jira Software issues synchronized with the information in your development tools – Fisheye/Crucible, Bitbucket, and GitHub. Instead of relying on developers to manually update the status of an issue after creating branches, committing code, completing reviews, or merging pull requests, you can configure triggers in your workflow to automatically transition issues when these events occur in your development tools. For example, you could configure a trigger to automatically transition an issue from 'To Do' to 'In Progress' when a branch is created. See Configuring workflow triggers <https://confluence.atlassian.com/adminjiracloud/configuring-workflow-triggers-776636696.html> for instructions on setting up workflow triggers." " Release Hub The Release Hub shows the progress of a version, so you can determine which issues are likely to ship at a glance. The commits, builds, and (Bamboo) deployments related to each issue are shown, helping you to spot potential development issues that could cause problems for a release. When you are ready, you can also release the version from the Release Hub. Doing this marks the version as complete, moves incomplete issues to other versions, and triggers release builds. Read more about the Release Hub here: Checking the progress of a version <https://confluence.atlassian.com/jirasoftwarecloud/checking-the-progress-of-a-version-764478137.html> How it works When development tools are integrated with Jira Software, a developer simply needs to supply an issue key for the issue to be automatically linked: - Commits are linked automatically if the issue key is included in the commit message. - Branches are linked automatically if the issue key is included in the branch name. - Pull requests are linked automatically if the issue key is included in the pull request's title or in the source branch name. - Reviews are linked automatically if the issue key is included in the title of the review, or if the issue is linked <https://confluence.atlassian.com/crucible/jira-integration-in-crucible-298977521.html> from the review. - Build linking depends on the tool: - Bamboo: linked automatically if the issue key is included in the commit message. - Pipelines: linked automatically if the issue key is included in the branch name. - Deployments are linked automatically if a commit involved in the build has the issue key in its commit message. Note that the issue key must conform to the default Jira key format – that is, two or more uppercase letters ([A-Z][A-Z]+), followed by a hyphen and the issue number. For example, ABC-123. When triggers are configured in the workflow for your project, particular events published by the developer tools automatically transition issues. Some details: - Some users who can see data in the Development panel may not have permission to see all the information in the details dialogs. This is because Jira Software checks for appropriate permissions in the linked applications. - The detailed dialogs (e.g. for commits) may display duplicates, although the number of unique items are reported at the top of the dialog and in the Development panel summary. Duplicate commits, for example, can arise from having Bitbucket Server and Fisheye linked to Jira Software, and Fisheye in turn connected with Bitbucket Server, so that Fisheye also reports commits. - If commits linked to the issue are involved with a Bamboo build that fails, the first successful build that follows will be reported, even though the original commits are no longer involved with that build. - The Development panel replaces the Source, Commits and Builds tabs, as well as the Deployment panel, in an issue. So, for example, you won't see the Source tab, and commits in Bitbucket Server will be accessible from the Development panel. However, if a connected application is older than the supported version, information from that application will continue to be displayed in those tabs rather than in the Development panel." Not sure if any of this is constrained by the JIRA / Github account / setup in use by Apache but it seems this would allow JIRA to see details from github. And/or maybe added JIRA apps to further integration (see https://marketplace.atlassian.com/apps/1219592/github-for-jira?hosting=cloud&tab=overview or https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?tab=overview&hosting=cloud [but this looks like it may cost for usage) Eric Bresie [email protected] On Thu, Nov 11, 2021 at 8:35 AM Eric Bresie <[email protected]> wrote: > Not sure if this would help in integration between existing systems but is > "autolink" enabled on github to ease references to NETBEANS JIRA tickets? > If not and the github product (pro, enterprise, etc.) in use allows its use > but if it does, it seems like it might help a little to put in a ticket > reference which automatically links to the JIRA ticket. > > For more see > https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources > > Assume if setup with a prefix of NETBEANS pointing to a URL something like > https://issues.apache.org/jira/browse/NETBEANS-<num> then references > starting with NETBEANS may automatically link up. > > That does assume a ticket exists to do so. >
