I have a nintex workflow set to fire when an item is modified. If the workflow modifies an item, will it trigger the same workflow again?
Once upon a time, yes; however, this was a bug. If you are running on the latest version, no.
At least, this is true of Nintex Workflow 2007 on our MOSS 2007 SP2 farm using the Set Field activity.
With SP 2010, Nintex does not offer the ability to disable event firing (like visual studio does). Therefore, starting a wf when an item is maintained is not a good option if the wf updates the item. It will trigger a loop.
Related
I have a requirement to update work item status to a ready for test state after the first successful release using TFS release management. It seems like there should be a straightforward built in task to do this but I can't see it. My current thinking is
Use TFS REST API to query the workitems and update them all using powershell
Wrap this up in a powershell task and include in the release definition
This will do the job I reckon. It's yet more powershell in our releases but they are built on a stack of powershell anyway so at least it's well known.
But is there a better (quicker) way to do this? If the answer is a straight 'no' then great - I will accept that answer gladly.
We are on TFS 2015 R4.
Many thanks for any/all help
Sorry, there is no out-of-the-box feature for this by Microsoft.
But we still could use some three-party extensions or tasks to handle this situation.
The WorkItem Updater task can update the following work item fields during a build or release:
Update the state for workitems linked to a build.
Update the assignee for workitems linked to a build.
Add the build as Development Link to the workitems.
The limitation is also very obviously, it could only update work items which be linked to a build. Which seems not be a problem, it's also a good behavior track work items during build pipeline.
Otherwise, you have to use the ways mentioned above to update normal work items after/during a Release.
We have a project on VS online that uses the Agile process template. We have configured this project to
.
If I create a bug, I can't unfortunately delete it afterward. The 'State' dropdown only includes the 'New', 'Closed', 'Active' and 'Resolved' values. This does not match with what Microsoft documents in the following page. If you look at the section labeled 'Q: What workflow states does Agile support?', it says that you can go from 'New' to 'Removed'.
Why I am not able to do this change? What can I do to remove bugs that were created by mistake or that were simply not valid?
Note that I am the administrator of the project.
Sorry about the confusion. The Removed state is not part of the Agile Process Template, and we will update the documentation to reflect this.
We will also fix the product moving forward to allow to remove bugs on the backlog. Keep an eye to the release notes (and subscribe to the rss feed) to learn when we have fixed it.
Ewald Hofman (TFS/VSO Program Manager)
I can get the same behavior with you, so I help you submit a feedback on Microsoft Connect website, you can track the feedback from this link:
https://connect.microsoft.com/VisualStudio/feedback/details/1986844
For now, you can delete the bug via destroywi command:
witadmin destroywi /collection:https://<your project>.visualstudio.com/defaultcollection /id:<bug ID>
I have created a Pre Operation Update Plugin that is Synchronous from the following tutorial.
http://crmbusiness.wordpress.com/2014/04/07/crm-2013-step-by-step-update-plugin-tutorial-using-the-crm-2013-development-toolkit/
It works fine when manually saving the entity. However it does not get triggered when a workflow updates the entity.
I do not have any check for Context Depth. Can a workflow call/trigger/fire a synchronous update plugin?
Thank You
Ian
In TFS 2012, there are "To Do", "In Progress", and "Done" columns on the board. I'd like to make two changes. First, add a new column called "Ready for Deployment" between "In Progress" and "Done". Second, have TFS set tasks in this column to "Done" when they are included in a build that finishes successfully. Is this possible?
Sure this is possible, but not how the standard process template is intended to be used. Normally you'd add a "Deploy" task under the PBI/UserStory/Requirement, if deployment of teh item is required. Then, when all other tasks are completed, you do the deployment and if that succeeds you close the parent Requirement work item.
That said, as long as you're not using Visual Studio Online, you can edit the process template of any TFS process to add as many states are you desire. Keep in mind that if you're using Reports, that these might break due to the additional states you'll introduce. This will require you to update the reports (and the standard work item queries and Excel reports) as well.
The Team Foundation Server Power Tools can be used to customize the process template in a graphical editor, which is usually easier than manipulating the WIT-templates manually.
Alternatively, if you're using TFS 2012 update 3 or later, you can add custom columns to the Product Backlog Board and use those instead.
I have installed TFS2012 on my server, now I need to achieve change tracking.I have explained the details below.
The whole idea of change tracking is, if I change the PBI/Requirement the all linked work items/bugs/impediments status should be changed or TFS should notify me in some way.
TFS will not automatically update one Work Item when a linked item changes. There is no functionality for that out-of-the-box. What you can do is configure an alert.
Or you can test whether the TFS Aggregator that exists for TSF 2010 (open source project) will work for 2012 (not officially supported). It can update child or parent work items when a workitem in the hierarchy changes.
What you want is not possible in TFS out of the box, but you can implement this with relative ease using a custom ISubscriber or a SOAP webservice. See the following answer on question regarding this.