Last modified: 2013-08-28 20:50:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55499, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53499 - Linkify references to Mingle
Linkify references to Mingle
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-28 20:36 UTC by Diederik van Liere
Modified: 2013-08-28 20:50 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Diederik van Liere 2013-08-28 20:36:57 UTC
Heya,

As more teams are using Mingle for running their teams the agile way, it would be useful to parse git commit messages for "card 123" or some other mutually agreed standard and link that to https://mingle.corp.wikimedia.org/projects/<analytics>/cards/123

The tricky part will be to determine what project a git repo belongs to. <analytics> refers to the mingle project code and hence should be treated as a variable. For analytics it's quite easy, all our repo's are under the analytics parent repo but for other teams this might not be so straight forward. 

Thx!
D
Comment 1 Chad H. 2013-08-28 20:42:16 UTC
This is basically not possible to do for groups of repos. It's either all, none, or repo by repo.
Comment 2 Diederik van Liere 2013-08-28 20:45:04 UTC
I guess repo by repo then :)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links