Can anyone tell us why our TFS 2018 (update 3) scrumboard hangs when moving task from "To do" to "In progress". It seems that the "In progress" lane is not automatically re-freshed.
It's working fine when tasks are moved between Todo and Done both ways.
Se the screendump below:
Related
In the old TFS 2013 days, if you wire up your automated test cases with MTM and run them via MTM, you can view all historical test results for each of those test cases in the Test Plan.
With TFS 2015 Build/Release + Run Functional Tests tasks, in MTM, you can only see the latest result. How can you view all historical runs of a particular test case? In the web portal, you can see "Test Runs", but there's no way to find just the runs pertaining to the particular test case in question.
I bumped into a workaround for this by accident. If I manually mark the test as Pass/Fail, then when I go back to MTM, and "View Results" again for this test case, it will all of a sudden display everything in its history, including the automated test runs generated by builds or releases.
It seems like a bug in the MTM UI, but this works for now!
I have some projects with the same Gate Profile and Gate Quality and Leak Period on Sonar, and same "parent projects" on Jenkins.
Jenkins is configured to build the projects every day as 1:00 AM and when there is a commit.
Recently, sonar reportered "new issues" on three of those projects, but on those three projects there was no commit between the builds (ie. the last build with success and the next build, that reported the "new issues", used the same changeset).
And the "new issues" did not show up in the same day (what would be expected if we changed some global configuration or made some update). For one project the new issues appeared 2017-02-11 01:20 for the second on 2017-02-13 01:00 and for the third on 2017-02-14 01:17.
There was no recently change on the configuration in jenkins or sonar (global or project specific), in special no new rule were added.
All "new issues" are from the same rule "Null pointers should not be dereferenced" (from squid) which was already part of the Quality Profile used before the "new issues".
I even compared the console output of the builds but there was no relevant difference on the sonar outputs (except for the timestamps and the "fail" in the and because there were "new issues").
How can I discovered what happended?
And is there a way to change the "creation date" of the issues?
(for now we will not fix that "new issues", becuse they are actually old issues - from old code - and we don't want to configure a specific Leak Period for those three projects, and we dont want to mark those issues as resolved...)
I have Continuous Integration Set up in Jenkins which is Triggered every time there is Code change, However if the change is done Frequently then the Test Cases from 2 Builds are stacking up. Is there a way to Cancel/Stop the Previous Builds Test Cases from Running, and just Continue with the latest Build
Try to use the 'Quiet Period' option. This is available from the 'Advanced' section of 'Configure'.
Here, you can specify how many seconds Jenkins should wait before actually starting its task after a commit has been made. So, if you provide 30 minutes (30*60 = 1800) as the quiet period, and you have made a commit at 8PM, Jenkins would wait till 8:30 PM before starting its task. In the meantime, if you make 2-3 more commits, they will be stacked together and considered during the 8:30 PM run.
Hope this helps
We have recently upgraded to TFS 2015 from TFS 2013.
We've also moved over a project to TFS 2015 (which has been running since TFS 2010) which is using agile process.
We'd like to make use of the task board to display bugs and tasks, and almost all of them are not linked to a parent yet.
When I go to 'Working with bugs'-> 'Bugs appear on the backlogs and boards with tasks'
I only see user stories appearing on the task board (and any tasks linked to a user story). Please let me know how I can configure unparented bugs and tasks to appear on the board.
You should install to TFS2015 Update 1 (or better to Update 2) in order to have the unparented bugs displayed in task board.
We started using TFS 2013 as bug tracker some time ago (about 3 months). Before this we used TFS only as source control (bug tracking was performed in another software). For now we have developed some processes. We would greatly appreciate any comments, that would help us to understand, whether this processes are right, or not. So, here they are:
General info:
We are developing one big product.
Our team has 5 developers and 2 QA's.
Often we release new versions each 1-2 months.
We have 1-week sprints.
This is how we use TFS:
We have one team project and a number of areas in it. Each area represents some part of the product.
Our team project uses Scrum 2.2 template.
In the team project we create a "big" iteration for each release (e.g. "Release 01.2014", "Release 03.2014"), which starts from the end of previous iteration and lasts 1-2 months.
We use 2 standard work item types: Tasks and Bugs
All bugs and tasks belong to the appropriate "big" iteration and area.
We use tasks in 2 ways: as a standalone work item for any improvements and new features, and as the child of a bug when fixing a bug.
To monitor current situation we created a bunch of queries for TWA. Some of them are shared (Such as "Bugs new","Bugs for testing", "Tasks in progress" and others), and some of them are created by each dev/QA (e.g. "My tasks in progress", "My bugs done" and others).
Here goes work process description for Bug:
-->QA (or dev) creates a bug (State: New)
-->QA (or dev) assigns this bug to some dev (State: Approved)
-->When dev starts to fix a bug, he does the following:
---->changes state of bug to Committed
---->creates child task and changes its state to InProgress
-->When dev commits some code, that should fix the bug, he bounds checkin to task (created on previous step)
-->QA understands, that bug is fixed and ready for testing, when bug is in Committed state and EACH child task is in Done state
-->QA tests fixing of bug:
---->if bug is not fixed he changes state of bug to Approved
---->if bug is fixed he changes state of bug to Done
This process looks not bad, and somehow works. But there is a problem with standalone tasks, which is created for improvements and new features.
And here goes process description for standalone Task:
-->QA (or dev) creates a task (State: ToDo)
-->QA (or dev) assigns this task to some dev (State: ToDo)
-->When dev starts working on this task, he changes its state to InProgress
-->When dev has finished working on task, he changes its state to Done
-->QA tests this task:
---->if new features work fine ?
---->if new features work with errors ?
Here is the main problem: how can QA mark Task as passed or not passed the tests?
How we resolved it for now: QA's marks tested tasks with tag "Closed", if all is ok, and creates child bugs for task if there are some errors.
But working with tags this way seems not to be good.
EDIT One more question: Which state of Bug/PBI is most suitable for state, when bug was assigned to developer, but he did not started working on this bug yet?
Any comments and suggestions will be greatly appreciated.
You are not using the Scrum template as intended.
The typical approach is to use Product Backlog Items to represent features, and child Tasks to represent the work necessary for PBI's or Bugs.
Teams will often have one (or more) tasks that represent the testing work that needs to be performed for each PBI/Bug. Then you can track if testing is done or not by looking at the status of the tasks.
Maybe more work/overhead than you're interested in investing, but have you looked in to using the "Test Case" workitem type? A couple fancy things about Test Cases:
They can be attached to a Task to specify the task is "Tested by" that test case
They can have results, making the definition of the test reusable across iterations
There's a bunch of built-in reporting for showing what the current status of testing is (passed vs failed vs not run, etc)
There's even UI for entering test results and managing test cases in the TFS web interface
Tests don't have to be automated, but it's nice if they are. You'd get all the above benefits even if you're only using "Manual" tests
More info here: http://msdn.microsoft.com/en-us/library/dd380763.aspx