In Team Foundation Server (TFS) 2017 commenting on changesets is enhanced with additional functionality supporting markdown, "# Mentions" that notify a person they were mentioned, and so on. There is also a nice drop down with status such as "pending", "won't fix" etc.
I've not found any documentation indicating how to leverage this, such as a list of "pending" comments, "won't fix" etc.
I'm utilizing TFS 2017 Update 2 on premise.
Any ideas on how to organize, review, and manage this? These seem completely separate from the "Request Code Review" functionality.
Code Review function requires Team Explorer/Visual Studio, it's a client based feature.
Adding comments on web portal is web based feature. You can only see them on web portal.
Regarding the status of comments on web portal, there are five status: Active, Pending, Resolved, Won't fix, and Closed. When you add a new comment, the status is Active. You could change the status to Pending when you work on this comment, if the issue/query in the comment is resolved, change the status to Resolved, otherwise, change it to Won't fix. After verifying the changes, you could change the status to Closed.
Related
I'm trying to have my company transition to JIRA from email for bug tracking purposes, and I can't figure out one thing: why JIRA (and BitBucket's Issues, which is sort of a limited version of JIRA) don't have a "Ready for retest" status.
I imagine the flow works like this:
Bug is reported
Bug is handled by developer
Developer marks bug as ready for retest
Tester tests, marks "Resolved" or "Closed" if all is OK, otherwise back to "Open".
Apparently I misunderstand something or other people don't work in the same way. What's the correct workflow status for the testers to retest the bug?
You, or your jira administrator, can create your own status in Jira. Look in Jira adminstration/ issues/ issue attributes and there you can add a status.
Then you still need to add that status to your project workflow, but that is another story.
Here is a link to help with all of it: https://confluence.atlassian.com/jirakb/define-new-status-or-steps-in-jira-workflow-718835875.html
Some organizations use the "Resolved" state to mean what you do by "ready for retest", then move the bug to "Closed" when the retest is successful. This would let you use the default workflow without adding states.
Currently, developers have to:
click on each card within the "In Review" status in the Jira Scrum Board
click on the "Reviews" tab
click on the review link
finally they are able to see who the reviewers are (if any)
I would like to be able to see, at least, the number of reviewers assigned to a task directly from the Scrum Board cards in Jira as this would be much more efficient than going through each card in the "In Review" status (there may be 20 issues at any given time). Developers would only care about those issues with less than 2 reviewers, so that they can jump in.
How can I achieve this? Thanks a lot for your help!
What you try to achieve (as far as i understood) is already available but depends upon the Jira version and the version of development tools connected with Jira.
Please see e.g. in the official doc: https://confluence.atlassian.com/jira/viewing-the-code-development-information-for-an-issue-445186939.html
Trying to sum things up:
With incompatible or just older versions of development tools (like FishEye/Crucible) or incomplete configuration in Jira you will only see 'Source' and 'Review' tabs which will not provide you directly with the informations you want.
In newer versions and with full integration, Jira does enable a 'Development Tools' panel. Clicking on one of headlines will provide you e.g. with status of reviews and the reviewers within (screenshot: https://confluence.atlassian.com/jira/files/445186939/jira-issue-devpanel.png)
I'm on update 4. I want to let business users submit "tickets" in TFS for research. However, they less rights to the project and aren't part of the contributors role. In addition, TFS documention indicates that once you deploy a "team alert" that the "#ME" variable changes to actually referring to the team, and not the person.
What is the approach to take to ensure that someone with less permissions, and not part of contributor group, will always get notified when a work item they created gets changed.
NOTE: TFS 2013 UPDATE 4 -- ON PREMISE
Related item: TFS 2013 (Update 2) Team Alerts not sending emails
* this doesn't help as I can't add them as contributors, need narrowing security permission.
UPDATE 2016-02-22
In looking through the alerts section, as an admin I see I can actually search and find an individual and setup an alert for them on the workitem change. However, this is a manual process, and I would like to do this in bulk. I will work on tracing the query execution that is called when the alert is created and see if I could replicate with a sql command to insert alerts for all users. However, I'd like to avoid running a direct sql query to do this if possible, if there is some bulk processing functionality that allows an individual alert to be deployed to each person on a team without doing it manually.
Anyone aware of any extensions, scripts, or other functionality that does this?
According to the comments of this issue TFS 2013 Update 2 Team Alerts not sending emails.This issue is not fixed with TFS 2013 UPDATE4. So, if you can't add the users as contributors, then they can't receive an email.
As a workaround, you can use events of team room. Adding events lets your team know when builds finish, source code is checked in, work items are updated, and requests for code reviews occur. This can be visible to all members of the team room. Detailed steps and more info from MSDN Collaborate in a team room
We have been using TFS 2013 for over a year now and have been using the Team Rooms (basically an IRC clone) without any problems. Additionally, I set up an automated build of our main project whenever anyone checks in a change. I then configured the Team Room to post a notification in the chat room whenever a build completed. Everyone appreciates this feature because it lets us know that there is a new update, and it lets us know if there is a problem compiling the current code base, usually prompting ridicule of the poor fool for being so careless.
Unfortunately, I recently took a two week vacation and while I was gone the Team Room stopped reporting build completions. Everyone claims there were no changes. I am the senior dev and the junior guys don't have access to the server anyway. I have verified in the "Manage events..." dialog that the room is still configured to post a notification when a build is completed, and I have been unable to find any trouble shooting guides on where else to look.
Is there a service I should be looking for? An error log somewhere? Has anyone else seen something like this?
Currently working with JIRA 5, I was looking for information about the handling Scrum in JIRA 6 with JIRA Agile (formerly Greenhopper). I saw, the there is now 3 statuses: To Do, In Progress, Done.
I find the 3 above statuses not enough. Particulary, we want to know if a story is still beeing clarified with the project owner, if is it a draft, if it has been approved by the customer. For a task, we also want to differenciate different steps in the "done" process: development done, review done, testing done, etc.
I'm looking for experience or any hints about this. My questions are: should I customize the workflow for my needs? Is there any standard workflows which already better supports Scrum? am I completly wrong and should I only use the basic concepts of JIRA for a Scrum process?
Any ideas/hints/experiences/links are welcome. Thank you.
You can customize the JIRA workflow (https://confluence.atlassian.com/display/JIRA/Configuring+Workflow) and then map the new statuses into Agile columns
In case if you already have a configured workflow go to your Agile board, go to its configuration and navigate to tab "Columns". On this screen you can add your custom column name, change its position and drag&drop status to a new column in order to map issues with this status to a column. If you use standard flow and need more customized one which better fits to your process then the link provided by mdoar above explains how to do this in details.