You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @bruno-morel, I was wondering whether there are any plans to support the automation based on mentions of a Jira key from github issue/PR/any others in their title(/desc/commit/others) as supported for a few years by the Jira/Github integration syntax.
This would help people who use Jira and Github to keep their workflows (as may orgs already do that to benefit from the development information integration) and avoid the inevitable scenario of tens or hundreds of labels on a github repo over time.
The text was updated successfully, but these errors were encountered:
marnovo
changed the title
Link based on Jira key mention rather than label
Sync based on Jira key mention rather than label
May 21, 2020
Sure. Not really difficult, but how do we limit it?
Just accepting a JIRA mention in the title description of the issue and not taking the comments into account to avoid spilling over into different stories?
Or do you believe that's too simple to meet your needs?
If not, do you have a more complex example in mind?
Hi @bruno-morel, I was wondering whether there are any plans to support the automation based on mentions of a Jira key from github issue/PR/any others in their title(/desc/commit/others) as supported for a few years by the Jira/Github integration syntax.
This would help people who use Jira and Github to keep their workflows (as may orgs already do that to benefit from the development information integration) and avoid the inevitable scenario of tens or hundreds of labels on a github repo over time.
The text was updated successfully, but these errors were encountered: