So, a project that I am working on requires the custom column/silo of 'ready' to indicate that the initial analysis has been done and it ready to be picked up as a development object. When I change the state of an user story to 'ready' it does not show in the appropriate column however when selecting another such as 'new' or 'active' it is displayed. Is there a word restriction on the use of 'ready' as a column (silo)?
Please make sure you have also configured the state mapping for your customized Ready column. Otherwise, if you change the state of work item it will not auto show in the appropriate column.
More detail about this you could take a look at our official tutorial Update Kanban column-to-State mappings
Related
I have been trying to switch to Azure Devops to manager our projects for quite a while now.
The latest hurdle is when viewing a Backlog item board.
The 'Planning Has Started' column does not work in our work flow, I have changed it to 'Paused' which means that items in that column have hit a road block and need attention.
But the 'State' when items are moved to that column still show 'Planning Has Started' and 'Paused' is not a option as a setting.
Where can I set/change the various States that are available?
I really have spent a good amount of time looking for this before asking here.
In your current situation, we recommend you check your state mapping settings in your Borad. Please make sure you have mapped the right state to your columns 'Paused'.
Then, if you do not have the state 'Paused', you can go to the 'Organization settings --> Boards process --> Your own process --> New state' to create the new state 'Paused'.
We have a typical board with the following columns.
New
Groomed
In Dev
Ready for QA
In QA
Ready for release
Released
When we click and drag a user story from one column to another, we'd like it to update the "assigned to" field automatically depending on which stage its in. We're not seeing any settings from which to accomplish this from the Azure DevOps UI. Any suggestions?
You could customize the Process to achieve what you want:
Customize States for each column in user story work item type (The process for your team project should be an inherited process). Go to the Organization Setting -- Process, choose the inherited Process your team project used, and then choose user story work item type. Click States tab and add appropriate states for each column. Check the following example:
Add rules for user story work item type. Click Rules tab, and add following rule for each State:
On Azure DevOps - I have created a custom work item with custom fields on the page or form of the work item layout. Now as per the process I need the system to freeze all the field updates on certain state Eg: Let's say all the actions on the work item is done then the work item state could be tagged as 'Completed' OR ' Closed' - Now here I need to know if there's any technique to freeze all the fields on the page or form at once. (One way to do it is to set the rules for all the fields BUT if there are over 50 fields on multiple pages of the work item then it may require to set 50 rules which seems to be not the right approach. Kindly suggest!
As far as I know, this should only be achieved by setting a work item rule. You don't need to set a rule for each field separately, just add multiple actions in a rule to make multiple fields read-only.
I'm using Azure DevOps Service (the on-line version, not on-premise) with Agile methodology.
I'm trying to add a custom state of 'Testing'. I use the method described here, but this doesn't seem to work. I can add Testing as a column in the sprint board, but it doesn't appear in the State picklist values (I do understand that adding a column will not add a State).
How can I get this to appear in the State picklist?
How can I get this to appear in the State picklist?
1.You can quickly navigate to the process your current project belongs to via Project settings => Overview => Project Details.
Then you can modify the states there. If you want to add a Testing state to Bug WorkItem type, click the Bug and click the new state:
2.And we should know that only inherited process can be modified in this way. So we must make sure our project is created from inherited process. Otherwise the New State button is disabled.
I have created a very simple workflow in Sitecore 7.2 (rev. 140228) which follows the out-of-box sample workflow exactly the same except that saving a "Draft" item doesn't also automatically push the item into the review state for a certain role. I have applied this workflow to the standard values item on a base template via the Default workflow field.
Whenever a user (non-admin) creates an item derived from the inherited base template, that new item's initial state as defined by the workflow is appropriately set to "Draft". I can then run that item through the workflow to reach the "Done" state. Basically, the workflow seems to work as intended!
However, when the user hits edit to create a new version of the item, the item's history then shows that user's item history as having "Changed from ? to Draft".
I cannot determine how to set the initial state of a given item's version to something that will not result in a version's state intially being shown as "?" in the item history.
As an example: I can (wrongly, I believe) set the State field on the Standard Values item for my base template (which many other items inherit from) to the "Draft" state but, when I check the Standard Values for the item templates which inherit from that base template, they don't inherit that value in the State field.
I can set the State field in the Standard Values for an item template itself and new versions of that item still show "Changed from ? to Draft" when new versions are created.
Can anyone explain how to get new versions of items to indicate in history that they "Changed from Done to Draft"? Is there something here I am missing entirely?
I've tried the suggestion from Jay below and the result is the same:
I modified the workflow as suggested
I start an item through the workflow, and then just run it through to "Done"
Go to edit the item (which creates a new version) and I'm still getting "?"
Just to add to this from the permissions standpoint, the two roles I'm testing this workflow with literally have full access to the workflow across the board.
I've noted that workflow state names show "?" when a role's access to that state is restricted in various ways, but I'm at a loss when it comes to why things aren't showing up properly with permissions as they currently are.
I think jRobbins has the size of it. While it doesn't really make much sense from the standpoint of user understanding, I can see why the workflow state is showing up the way it is. I can only hope that Sitecore will look to provide a way of addressing this in a more simplistic manner in the future!
By design, the new version of your Item is created in the Initial State of its Template's Workflow, not the state of it's the previous version. Therefore you will not achieve your desired "Changed from Done to Draft" entry in the Item's history.
I agree that "Changed from ? to Draft" is not an accurate entry but I think you may have to live with it unless you want to write some custom code on the function that creates a new item version.
Additionally;
"As an example: I can (wrongly, I believe) set the State field on the Standard Values item for my base template."
You are correct, setting the State field of the Standard Value of the template actually enters that Standard Value Item into workflow itself. You should only be setting "Default workflow".
See this link for more info - http://sdn.sitecore.net/upload/sitecore6/workflow_cookbook_a4.pdf
In Sitecore's default workflow, the __OnSave command is in Draft state and __OnSave's next state is Draft again. In this case, item's version information is "? to Draft" because "Draft to Draft" doesn't make a sense.
I created a new workflow and make __OnSave command to reside in Approved (Done) state. This __OnSave command's next state is "Draft". So, you will see the item's version information as "Done to Draft"