I created a new Sprint, assigned Issues to it, however on the TaskBoard it does not allow me to drag the issue to the correct location (ToDo,Doing,QA,Done):
Any idea why is that happened?
However, If i create a new issue with the + button, it is created on the "ToDo" column and it allows me to move to other columns.
It does not allow me to move existing issues (like the 707 on the picture) to the correct column (QA in this case)
Thanks!
Related
My current requirement is to create charts out of queries in Azure DevOps (for ex. pie charts) that visualize certain work items and group by the Area Path of the work items. However, the grouping in the chart should only consider the first sublayer. So for instance, it should only consider root-path/x instead of root-path/x/y and root-path/x/z individually.
The only solution I could think of so far was to consider the Team-field instead of the Area Path-field as a team should be associated with every subpath, but apparently, teams aren't associated with work items and the Team-fields in the result of my queries remain empty.
Is there an other solution or "workaround" to my problem?
I searched and tried other Chart extensions, but none of them can meet your demand.
When selecting "Group by Area Path", they always list all the area paths of the work items from the selected queries.
I also checked 'Project configuration' and 'Team configuration' on 'Project Settings', but did not find any option can affect this.
Looks like, we currently have no any available solution or workaround that can group work items by only the first sub-paths of the root area path on the Chart for work items.
Maybe you can try to develop a custom Chart extension following your demand.
I am having backlog in TFS 2018 and I am using default template provided to create the tasks.
The template is having the 'Activity' drop down, while selecting the 'Activity' it is also renaming the Task Title. It is ok if I am adding the task using TFS.
Now, I am using the Excel to create the tasks in the user story.
Only problem is whenever I publish the list, it is renaming the Title of the tasks with Activity name.
For example, If I publish the following list, "My Task" will be renamed with "Requirements- Review" (Value in Activity Column) in TFS board under "My Userstory".
Is there anyway to disable this behavior while adding tasks using the Excel?
As per my understanding both Titles are required as it is creating the
Parent Child relationship. In Excel I am selecting Title 1 and
clicking on "Add Child" and it is creating Title 2 column.
Actually we do not use this kind of way to add a nested list of work items( Parent Child relationship)
For example, you should first convert your flat list to a tree list by adding a tree level.
Enter titles for backlog items under Title 1 and for tasks, under Title 2. Also, select the corresponding work item type for each. Here we specify Task.
Publish your worksheet and the ID 95 is new created through Excel. In the background, parent-child links are created for each task listed.
As you can see in web portal, the new create task is list properly and title do not change and activity is also right.
More details please take a look at this official tutorial-- Bulk add or modify work items with Excel
I am setting up a SharePoint app/list to house my business team's project proposals for the next budget year. I've created a custom content type (named CostProject) that has several columns in it that describe our cost projects.
Because we plan on using this process for years to come, I'm envisioning a structure where CostProject is the generic content type, with sub-content types for each budget year (2018 CostProject, 2019 CostProject, etc.). So I created another custom content type (named 2018 CostProject) that inherits all of the columns from CostProject.
Now I'm trying to create a list of all of these cost projects. So I added a new app (type: Custom List) and named it ITDD Cost Projects. I went into list settings >> advanced settings and checked the option to "Allow management of content types." Back on the list settings, I scrolled down to the content types section and clicked "Add from existing site content types."
This brought up a form where I could select various content types, so I selected 2018 CostProject from the available content types and clicked "Add >" then clicked "OK." After clicking OK, this is the error I get every time:
"The formula cannot refer to another column. Check the formula for
spelling mistakes or update the formula to reference only this
column."
Thinking this might have something to do with the syntax of one of my calculated columns, I went back the CostProject content type and removed all of the calculated columns (copied their formulas, etc. into a document so I can come back to them later). However I still get the same error message every time I try to add the content type to the list.
Any idea what I'm missing here? I'm pretty new to SharePoint so perhaps it's something basic--any help would be greatly appreciated!
THANK YOU!!!
So for the sake of people not reading comments. When you encounter an error which states that:
The formula cannot refer to another column. Check the formula for
spelling mistakes or update the formula to reference only this
column.
You should check your validation formulas on columns.
It may occur in different situations, but the core issue is that field cannot be added to list:
Here is reported bug when creating list from template and this is possible workaround.
I would like to premise that I am not a coder, and have limited SharePoint experience. Nonetheless, I have a task at work to create a new tool for a group at work. This tool will allow them to track things through its life-cycle. The old tool will stop being used once they hit the 49,999th record. At that point we will transition to SharePoint. The prior numbers will live with those records and we will be unable to start back at the number 1.
My goal is to have an ID field for each record that incrementally grows starting from the number 50,000.
I tried creating a new calculated formula field that does 50,000 plus the ID but it does not work effectively. There tends to be a lag. The lag can be anywhere from 5 minutes to a day or two. In turn, I need an alternative option.
With a friends coaching, I am messing with SharePoint designer to automatically create a record once one is deleted and delete one every time one is created. However, this times out occasionally. Even more so, it is extremely slow. It will take me a week or so to get to 50,000. Does anyone have any experience or expertise to assist me? It is very appreciated.
The way I did it was to create another field and used that in all my views. Update it through a SharePoint Designer workflow on create - set the field to ID+50000, for example, or whatever you need. Maybe give it a bit of a buffer and set it to ID+51000. By the time the workflow is running the ID has been created and you can use it in a workflow.
If you are going to be moving your old records to the list, you can change the workflow to only update the new field if it's blank. That way you can save the original ids.
In VSTS Online, using BoardColumn as a Query Criteria, or using it as a Column in Query Results, does not work.
For instance, we have custom columns, beginning with Committed, and progressing through additional states. It seems that the system only allows us to query using out-of-the-box column names, that match State values.
If I query for BoardColumn = Committed, the query returns Work Items that are in the Committed Column, or any of the subsequent columns, and the displayed value for BoardColumn in the query results simply says "Committed", because that is the State value on those Work Items.
Additionally, using one of the custom columns, such as "In QA", as a criteria value for Board Column, returns zero results, even though there are Work Items in that column.
This does not make sense. Why does the query functionality not actually look at the BoardColumn value when querying? Why does the query result display State instead of BoardColumn?
A few weeks ago I ran into an issue similar to this. We had our team split into two, and one of the new teams was using the Kanban board. For the split we used the information on Visualstudio.com
We noticed that, whilst the items were positioned in the correct board column, any queries would give the old state (i.e. Committed).
A hint to the problem was found on visualstudio.uservoice.com where they were discussing which teams owns the item. Eventually I realized that, whilst our two new teams both had their own backlog iteration, so did the old 'root' team. Changing the Backlog Iteration path of the old team to some subiteration solved the problem for us. It seems the old team was still considered the owner.
The question seems to be: is your Work Item also visible on another Board? Then this might be the solution.
This is all TFS 2017 on-premises.
It appears that VSTS will save the board column information for the Team that "owns" the item. It's possible to move the item across different boards at different Team levels, but the query result reflects the team that owns the item. For example, if the item belongs to a Team's area, then it's placement on the board will be reflected in the query. The parent Team's placement on the board will not be reflected. This is true if you have nested teams/areas as well.
when a team is configured the area and iteration path are mapped, if the team's area path includes the sub area paths and there is a seperate team configuration/board for one of the sub area path then you might see this.
you can exclude sub area paths from this team settings and doing so will have your workitem being mapped to a single area path which is mapped to a single team board.