Linking source files to cards
Mingle integrates with your team's source repository to link your code to cards. By typing card numbers in the source commit messages, Mingle automatically links code revisions with the cards that are referenced. All code revisions are also linked to Mingle's History tab, so you can always see what code changes happened relative to other changes in the project.
To use this feature, you must have successfully integrated your source repository with Mingle.
Mingle's Source tab lets you browse your entire source repository and shows
- code revision numbers against each directory and file
- commit messages (including links to cards if card numbers were entered in the commit message)
- when the source file(s) were committed
- the name of the person who committed the source file(s) (setup your source repository user name in your user profile).
Mingle's source repository integration is a great way to help new team members easily discover the code used to implement business requirements.
Mingle automatically scans all files in your source repository (based on the local directory path specified under Project admin tab, Project settings link), and displays all revisions on the History tab.
From the Source tab you can click on a revision number to view the source files that were changed in the revision and the actual changes against the previous version (diffs).
How to view details of revisions in your project's source repository
- Sign in to Mingle and locate your project (if you're not already working in the project).
Click the Source tab.
Mingle displays the highest level of your project's source repository, showing the most recent source file revision.
If you want to
view the details of a specific revision, type the revision number in the Choose revision to view field and click the Go button.
Mingle displays that revision of the repository. (Type HEAD and click the Go button to return to the latest revision.)
browse details of changes within the source directories, click the Filename link
Mingle displays the contents of the selected directory with details of each file/folder's last revision.
If you want to display more details about specific changes made during a revision, click on a Revision number.
Mingle displays a list of all changes committed in the revision, including a list of all files.
If you want to
view details of the actual card (e.g. bug or user story) referenced in the commit message, click the links to those cards (in the screen shot above #1708 and #1711).
Mingle displays the details of the selected card.
view specific details of the changes to a source file between this version and the last version, click the View diff link.
Mingle displays details of the source file changed, added or deleted.
view the actual source file, click the View source link.
You can download a copy of the source file by right-clicking and selecting Save Link As... (or equivalent).
- view details of the previous or next revision, click the Previous revision or Next revision links at the top
- view a history of all revisions checked in, click the Revisions link
- return to the latest revision, click the Source link.
Using card keywords in source repository checkin messages
Before you can link card numbers to source repository messages, you must setup appropriate keywords so that Mingle identifies card numbers correctly and establishes the links between card numbers and code.
For example if you have a keyword of
#1in a commit message automatically creates a link to card number 1. When you're editing card number 1, you'll also see the source version and commit message in the card's History tab.
In the History tab for Card 1 above, you can see that Revision 937 addressed some aspect of this card (story 1). Clicking the Revision 937 link would take you to the Source tab where you could see all source files changed for that revision.