This is regarding Sonarqube 5.1.1 and JIRA 6
I'm working with Sonarqube's JIRA plugin for linking issues from Sonar to JIRA, and I was wondering if it would be possible to not only link issues to JIRA as the predefined JIRA user for Sonar, but if it would be possible to create the issues in JIRA (from Sonar still) as the user that is logged in and clicking the "link to JIRA" button on the issue.
My issue with how it's currently set up is that the reporter will then always be this predefined JIRA user for Sonar, and quite frankly it'd be much more useful if we also knew who was the one actually reporting the issues.
TL;DR I'm wondering if instead of a centralized, predefined JIRA user for Sonar, I can get each Sonar-User to also be able to report the issues.
Related
I have issues reported for my project through PMD analysis and am allowing sonarqube to consume the report through external properties.
Now I can see the external issues in sonar UI, but am not able to change the issue status from open to confirmed…there is no dropdown available.
I am using SonarQube 8.5.1 version.
Could someone help how will be able to change the issue status for these?
see here
There are a couple of limitations with importing external issues:
you can't manage them within SonarQube; for instance, there is no ability to mark them False Positive.
you can't manage the activation of the rules that raise these issues within SonarQube. External rules aren't visible on the Rules page or reflected in Quality Profiles.
We have recently migrated to jira agile and the issues have changed from tasks bugs to stories. We have been using maven changes plugin to automatically send notification for new releases and it successfully includes issues resolved and so on. Now that we have stories, it does not include them to the message body. I have updated the configuration properties to include stories also and all possible issue types (Bug, New Feature, Task, Improvement, Sub-task,Story) but still no success. The jira report that is generated by the same plugin is correct but the mail still does not include them.
I also tried to attach the jira report (${basedir}/target/site/jira-report.html) but with no success.
Can anyone propose a solution or a work around too this issue?
After some further research and a lot of code checking in the source code of maven changes plug-in I found out that you have to include the following mapping in your configuration
<issueTypes>
<add>Story</add>
<fix>Bug</fix>
<update>Task</update>
</issueTypes>
This will inform the maven changes plug-in to map the build in xsd add,fix,update to Story, Bug, Task issues that are created with agile jira
Indeed, I have found Developer Cockpit Plugin which is commercial one. But I would like to know is there any alternative with simple features (None Commercial) to apply?
Use an SCM Plugin (e.g. Git Plugin) and you'll immediately benefit from the auto-assign feature: if the committer of a line with an issue matches a SonarQube user account, issue will be automatically assigned to that user (who can see his issues from his User Account). Not to mention all the issue filtering that you can then do by author.
We are trying to install a CI Platform with (Jenkins,sonar,eclipse ...).
So that every developer can make analysis on his code before commit, I'm wondering between two alternatives :
running local analysis with the sonar plugin.
install the different plugins that sonar use (findbug,pmd,checkstyle ...) and configure them to meet the sonar configuration.
I'm not sure which alternative to use? I used to work with findbugs,pmd, checkstyle in eclipse and they look great.
Can you tell me which is the best alternative?
Thanks in advance.
Regards.
With Sonar plugin you can manage the violations like:
Create a review
Mark a violations as false positive or fixed
View the hot classes and hot violations
View yours reviews
If you use separate plugins you have to go sonar web to do that.
The great advance of sonar is the reviews.
Other question is how many projects you have and will have. I currently work with more than 70 projects and many profiles. Is more simple to me run analysis with one plugin, because I need just add the server and find the project. With other plugin you need add the link for each project in each plugin configuration.
Why not install the Sonar Eclipse plugin?
This was designed to solve the following problems:
Sonar does not support parallel analysis of the same project. This issue rules out the option of each developer running Sonar locally. (See SONAR-2761, SONAR-3306)
You don't really want developers uploading metrics and source code into the Sonar database. They could be working on an uncommitted workspace and would therefore cause both inaccuracies and confusion if Sonar is being used for code review.
Sonar is really designed to be run from a continuous integration server (like Jenkins), building code that has been submitted onto a shared codestream (or branch)
The big advantages of using the Eclipse plugin are:
True local analysis, no updates of the Sonar database
Configuration of the other tools is retrieved from the Sonar server and jars automatically downloaded.
Centralized management of Sonar quality profiles
At work we thought it would be nice to track our performance statistics on a daily basis with Jira. We already have an automated testing suite, but ideally we could link this to Jira ticket spanning a project, and every day the automated results would be added to the top level ticket info, and a comment or subtask would be created with detailed stats and detailed performance analysis by an engineer.
Does anything like this exist, or would this require writing an actual jira plugin?
I think you are talking here about some unusual usage of JIRA. Normally, you have a lot of tickets to a project, and not 1 ticket "spanning a project". Here are some hints what could be available (depending on the other software your are using):
If you use a build environment like Hudson or Jenkins, there are plugins available to link the fixed issues to the build where the fixes were made. See "Jenkins JIRA Plugin" for some more information. So if you have a nightly build (once a day), Jenkins will give you a list of JIRA tickets that were worked on.
JIRA itself has a lot of charts that may be worth looking at. So e.g. the "Created vs. Resolved Chart" shows you the tickets that were created anew and were solved on a daily, weekly or monthly basis.
Eventually, the data you search for is available as a gadget (see the documentation). Then you can add that information to your dashboard by using the normal mechanisms of JIRA.
None of the tips above does exactly what you want to get ...