In the Work Item type like Bug or Task the start date allows to select any date however we want the Work Item allows the start date to be in the date frame set for a particular Iteration.
how to set such a rule for Work item in TFS?
Unfortunately there isn't such a rule/feature in TFS can achieve that, we can only apply an existing field rule to a work item type, please see Add a rule to a work item type
So as a workaround you can write you own rules using TFS Aggregator just as #Jayendran mentioned.
You can also try another workaround:
Instead of entering the start date, you can auto fill the Start Date field on some event (eg: when changed the state from "New" to "Approved").
For example we first open the work item and assign to Developer. When he is ready start working on the task, he will change WI state from "New" to "Approved". In this case the start will pick the current date & time. when he done the development, developer will change the WI state to "Done", and the end date will pick the current date & time. Thus the work item within the particular iteration, so the actually Start and End date will also between Iteration Dates
Related
When I use Auto-Schedule in JIRA Advanced Roadmaps for
an Epic with four stories where some stories some have subtasks
where every subtask has estimated hours
no sprint is assigned to the Epic, Stories or Sub-Tasks
where the Epic is assigned a Start Date of 6/1/2022 (in the Roadmaps field configured for "Start Date")
The proposed schedule generated doesn't begin on 6/1/2022. Instead the next business day is used. In this example it starts on 4/26/2022.
How do you tell Auto-schedule to start on a specific date?
The only way I know of setting a start date will affect all epics:
Go into your advanced roadmap
Click on the three dots right from your roadmap name
Click on "Configure"
By default the "Scheduling" settings should open
There you can set the start date.
When you are looking to provide a start date for an Epic/Issue, then this is not possible at the moment: https://jira.atlassian.com/browse/JSWCLOUD-22406?actionOrder=desc
I have two tables in data studio:
I'm asking the user to select two dates to compare two weeks. This way, we can see the two weeks' data side by side. However, I also want to see the percentages of change based on vendor. Is there a way to show this? Or how can I improve the comparison method ?
note: vendor name field is not fixed. it can change for every week.
Data Studio provides a way to compare current date with previous one, but the comparison parameter will be fixed (eg. "current week vs previous week", "current month vs 2 months ago"). That means you won't be able to drop a selector for your users.
With this feature you to select the current date (or a range of dates) and it will always compare to the period you choose in design view. (I usually select the option "previous period", so if the user select a week, the comparison will be with the previous week; if the user select a month, the comparison will be with the previous month).
To achieve this, just check this entry in the documentation.
Another limitation is that it will always display the difference between current value and previous value (delta). Currently, you can't change this behavior.
I know you can query by state change date instead of column change date if you are using the default columns that match the state. But our TFS board columns are custom. I can see the board column changes in the work item history, so they are clearly stored somewhere. I'm happy with help on a query or if there is some way to do it through the query tool that I haven't figured out.
Thanks.
You can only list work items with Kanban query fields, but can't get column change date.
You need to use TFS api to get work items revisions, and check whether System.BoardColumn field is changed in any revision.
Is it possible to execute a TFS query and get the results not for today but for a previous date?
I just want to see the results that were available in that date.
To clarify: I need to see the state of the work items on a give date to see their evolution over time.
According to your clarification, you need see the state of the work items on a give date. There is not a direct way to achieve it in Work Item Query.
You can only use Was Ever in Work Item Query to list items based on State past assignments, like:
state Was Ever Active
Or you can use State Change Date <= YYYY-MM-DD and State Change Date > YYYY-MM-DD to list all work items that changed State on YYYY-MM-DD. (Need to check whether TFS 2010 has State Change Date field)
Of course you can combine other clauses to narrow down the query.
What you want is actually the work item history. You need to get the work item history programmatically using TFS API. You can check this blog below to use the API:
http://www.codeproject.com/Articles/243653/TFS-SDK-Work-Item-History-Visualizer-using-TFS-API
I think you can create pivot table report to connect to TFS cube. For your requirement to see work items' evolution over time, you can define the pivot table as:
Check these two links for the details: https://msdn.microsoft.com/en-us/library/ms244678 and https://msdn.microsoft.com/en-us/library/ms244710.aspx
I have a simple workflow that runs on Create. If field X is yes, change Allow Email to Allow.
I have also created a personal view with criteria Fields X = Yes and Allow Email = Do No Allow. This is to give me list of contact that missing out.
Looking at last 7 days records, everyday this workflow runs on around 600 new contacts and updates fields as expected. But I also noticed that small number of Contacts (about 30ish per day) do not get their Allow Email field updated to Allow even when they meet the criteria of the if condition.
At this point I checked at the WF history and very strangely it shows that the field should have been modified. (see screen shot)
Workflow did fire off
This contacts are not modified by any process or individual since the workflow had run
Workflow shows the usual green tick indicating that it did meet the criteria
Same workflow also updates 'Preferred language' and that seems to have updated fine for these contacts.
I have also double checked the Update property to make sure it set correctly.
Has anyone else seen this? This makes WF not 100% reliable for me!
Your workflow runs on Create.
If the record is created with Field X to No the workflow doesn't change the Allow value.
If a user change the Field X value to Yes after the record is created, you have the situation with records Field X Yes and Do Not Allow.
You wrote:
This contacts are not modified by any process or individual since the
workflow had run
to confirm this, did you check that the ModifiedOn date equals CreatedOn date? I suggest to turn on audit for Field X.
My guess is that you didn't set your workflow to run also when the Field X value change (and it should)