How to link the issues in Bitbucket?
I already use the milestone, component and version fields, but i need to mark issue as depend on #125 or blocked by #1220.
How?
Update
I can place link #1 in issue comment, of course, but:
Comments are scattered throughout the whole issue log.
Linked issue doesn't knowing about it.
So, I've search for linked issues\tickets fields, like Bugzilla/Mantis/OTRS do. Or Linked and Related in Stackoverflow itself.
UPDATED
Simply use the # and BitBucket will link automatically to the issue, as you know.
The linked issue isn't aware it was linked (as on GitHub, for example): it's the BitBucket behavior.
Related
I am trying to report what I believe is an issue with RPMfusion.org repository, regarding the build of VLC therein.
Since the repository has hundreds of packages thereon, there seems to be nobody who wants to claim ownership of items posted there.
Rémi Denis-Courmont #Courmisch · 4 minutes ago Maintainer
Sorry but this is not a suitable venue to report issues with RPMfusion.org, which people here have zero control over.
After several attempts at emailing individuals at RPMfusion.org, I tried posting the issue as an issue in the code repository at videolan.org and got my finger smacked again.
My issue is that hundreds of downloads from the repository are getting a version of VLC that cannot properly play DVD menus. This only happens for those using the repository, so that rules out Windows and other non-RPM repositories.
I have about three pages of screenshots and instructions to quickly reproduce the problem. I think it may be a build issue, but cannot prove that to be the case.
Videolan.org doesn't want it: https://code.videolan.org/videolan/vlc/-/issues/27030#note_328247
RPMfusion.org by emails tell me "it is a package maintainer issue", and they don't want it. [[private emails]]
Anyone know anyone who might know who maintains VLC on RPMfusion.org??? Or where I might best post that question to reach a proper audience?
There is a VLC tag here, but not an "RPMfusion" one.
Thank you.
I have a C++ Github project and I would like to:
lower the boundary for people to contribute, but
keep the clang-format styling enforced
I am wondering if there is a way for me to have Travis to automatically apply (formatting) changes to people's PR. Looks like this is technically possible according to these github help pages, but I cannot find an example.
Has anyone ever tried this and could give me pointers? Or is there any project that already does this?
I would like to exploit the integration between the two tools to be able to automatically create a branch in GitLab for every new Bug or Feature ticket created in Jira.
I would like to know if (i) it is possible; (ii) what is the link between the two tools (I guess the unique ID number assigned by Jira); (iii) assuming the first point is true, what happens to the created branch when I close the Jira issue (e.g. I've mistakenly created a bug fix that was not needed).
I've used Jira in conjunction with GitHub so I'll try my best to help you.
I) This is definitely possible.
II) We used to use the unique ID given to a ticket and include it within in the branch name this creates a link between both tools. Any changes committed on the branch will be shown in JIRA.
III) From experience when this happens the branch will persist and will need to be deleted manually using a console we used to use a .git console and used a delete command.
I also found through a quick google search some documentation on GitLab on integration with JIRA as well as some insight on creating branches.
Doc - https://docs.gitlab.com/ee/user/project/integrations/jira.html
Branch - https://gitlab.com/gitlab-org/gitlab-ce/issues/3886
Hope this helps.
everybody. I've the following issue, when someone makes a new pull request and I leave certain comments, if this someone, does update the pull request, TFS instead of moving my comments with the code changes, it is left on the line number, rather than the code snippet.
If someone knows how this to be fixed, as it cause enormous efforts to track if the issue was solved.
Thanks for reporting this issue.
This is a new feature that is only available in TFS 15 RC1 and VSTS. Older servers do not have this feature. This feature is called comment tracking and it is mentioned in the release notes here.
When you click to add a comment as the screenshot below, you would be able to add a comment for a line of code:
Then you'll see your comment under the line:
I would like to get the issue list from Bugzilla and JIRA for an open-source project. For each issue, I'd like to collect the corresponding compilation units(for java projects, class/or interfaces files), which may relate to the issue.
Any idea on implementing this feature would be appreciated.
Many thanks!
For JIRA, there are some solutions out there you could use out of the box. See the documentation to integrate with source control for JIRA how to do it. This only works for some source control systems, you should which ones are supported. This gives you a list of change sets (e.g. for Subversion) for each issue.
Another approach could be to do it on your own through an interface to the source control system yourself. The following prerequisits have to be in place:
Your developers have the tools to add the information which issue was worked on by which commit on a per commit base.
You have rules that changes to the sources should all the time being done only for one issue at one time.
You are able to parse the additional information you will get from your version control system e.g. by a script or a program.
For Subversion and JIRA, it could work like that:
Ensure that all commits are only done if the Subversion commit message contains at least one JIRA ticket number. You may even ensure that by a pre-commit hook
Learn how to get the following information from the subversion log
The ticket IDs (by parsing the message) for each change set
The files that had changes for each change set
Collect for each file all tickets.
Show them in a format you like.
I think that this is not too useful, because ticket per class is too fine grained. Perhaps you should have a mapping of the files to modules, sub-projects, ... and collect tickets for them.
All solutions will be different depending on your selection of tools. JIRA and Subversion are here just examples :-)
The best way is to first integrate your issue tracking system with your source control. That means that whenever a developer commits a new change, it determines the set of issues related to this change. This linkage is managed by your issue tracking system and it can show you all the source files, resource files, config files that have changed in the context of an issue.
This info, will be available through the api of that issue tracking system as well.