Allow issue_regexp to define its own capture group

[timthesinner]

Checklist

• [x] All new jobs, commands, executors, parameters have descriptions
• [x] Examples have been added for any significant new features
• [x] README has been updated, if necessary

Motivation, issues

The current implementation assumes that issue_regexp is its own capture group. This prevents custom regex that include match conditions that are outside the group. For example it should be possible to define an issue_regexp like: .*?\/{0,1}([A-Za-z]{2,3}-[0-9]+) which will match eng/FOO-123 but capture FOO-123 which is a valid JIRA issue tag.

https://jqplay.org/s/ep4KfBKqPb

Description

Allow users to define a custom capture group in the issue_regexp

[KyleTryon]

Hello Friends 👋

The day has finally come 🎉 ! As we have alluded to in a few spots in this repository, we have been working on a new integration for Jira with CircleCI to replace this outdated orb which has historically been difficult for us to update. Today we are excited to announce Jira Integration V2 is finally LIVE!

New Docs: https://circleci.com/docs/jira-plugin/ Orb v2:

• Registry: https://circleci.com/developer/orbs/orb/circleci/jira
• Source: https://github.com/CircleCI-Public/jira-orb

Atlassian Forge App: https://github.com/CircleCI-Public/circleci-for-jira

Key Features

• Open-ID Connect Authentication - No Personal Access Tokens or API keys!
• Fully open source orb with Atlassian Forge backend.
• Optimized orb experience, now much easier to configure.

What to know

• This repo (https://github.com/CircleCI-Public/jira-connect-orb) will be archived shortly.
• We have attempted to address all current issues with this next generation integration. If you experience any issues or have any feature requests please open a new issue in the new repository.
• A video demonstration will be coming out soon.
• We highly recommend moving to v2 of the orb as soon as possible.