Missing pools in Toloka - pool

When I check my old projects in Toloka, I can't find pools: the interface doesn't show them. Do you know where they are? And how do I know why a pool was archived and its archiving date?

By default, archived pools aren't displayed in the list of project pools.
To see them:
o Open the project page.
o Click the "Show/hide filters" button at the top of the Pools table.
o In the "Status" filter, select "Archived".
You can only find out the date of pool archiving in the API. Get a list of operations with the type POOL.ARCHIVE
Missing pools in Toloka

Related

Why don't I have have permission to add Project Work Items in Azure Dev Ops

I am the owner of an Organization and the project within that organization, but I am not able to see the Add button for work types.
What permission needs to be set for me to have this ability?
You are trying to edit a base process. You have to create a child process first: Create and manage inherited processes
You can't edit the built-in process types. You must first create an inherited template. You can edit that and then switch the process type of your project.

Manage versions with Azure DevOps

I currently use these tools :
Azure DevOps - Only for Git repositories
Jira - To manage tasks / bugs / versions / customer requests / ...
TeamCity - Continuous integration (build and deploy versions )
I would like to replace Jira with Azure Devops (but continue to use TeamCity for builds for now.)
I already created some teams / areas / user stories / bugs.
But I would like a simple way to handle versions. For example, I fix some bugs and release a new version using TeamCity (ex. : v3.1.1.1234 ). How can I update my user stories / bugs to say that it is fix in this version ? There is no "Fix version" field like in Jira...
Should I use "Iterations" or just "tags" ?
If I want to generate release notes for the new version (for internal use), do I have to use Azure DevOps queries ?
You can create a customized field (ie.Fix version) for User Stories in azure devops. You can follow below steps:
1, Create an inherited process. (only an inherited process is allowed to create custom field)
Organization Setting--> Process under Boards--> Select the Process--> Click 3dots(...)-->Click Create inherit process.
2, Create customized Field for the inherited processs which created above
Choose your inherited process, and then choose the Work Item Type (ie, User Story)you want to customize.
Click New field, type in the new field's name (ie. Fix Version) in the Definition section. (you can decide where the new field should locate in Layout section or keep the default layout).
3, Change your project process to above inherited process.
Choose the process that contains you project. Click Projects-->Choose your Project-->Click the 3dots-->Click Change Process
You can check the document here for more information.
After you finish above steps, you will see the new field Fix Version in User Stories edit page.
If you find above steps complicated, you can just use tags.
#Levi Lu-MSFT, This only lets you create field in one workitem type if you want same field in Bugs, Features, Stories it wouldn't allow, it'll throw 'Field already exists" error.

Is there an easy way to re-run failed external data sets?

I've got roughly 60 files that didn't turn up when they should have done and therefore data factory has missed their arrival and marked them as failed validation.
To rerun, the only method I know of is to either click each individually and then "re-run" in the azure portal or use powershell.
Is there any way to bulk rerun in the azure portal or is there any way to re-run external sources in the monitor and manage application?
In the portal, click "Monitor & Manage", this will open in a new tab.
Filter the activity list to show the ones you are interested in (filter pipeline, status etc); then select multiple rows with shift+click or ctrl+click. THen click the "Rerun" option in that window....all rows selected will be rerun

How to customize workflow in Azure DevOps Service (VSTS online)?

I've read all the MSDN docs, but cannot find a way to edit the work item transitions in Azure DevOps Service (VSTS online).
I'm trying to:
Add a custom Reason to a State of a work item. (e.g. "resolved", "won't fix")
See/edit all the existing rules about how states transition.
This is possible if you are on the Hosted XML Process model in VSTS.
Hosted XML process model concept - VSTS
When are you on the Hosted XML Process model you ask??
Well after lots of reading I found the following note on the page explaining Hosted XML customization which states
Feature availability: Import process supports the Hosted XML process model which allows you to manage customizations through updating select XML definition files of a process template. This feature is only available for accounts that have been migrated to VSTS using the TFS Database Import Service.
But since I didn't import my VSTS I'm on the Inheritance Process model.
Which does NOT currently support this feature as confirmed here in comments
#RohanDaniel #ehofman#MSFT #DevMarTechOps You are correct. Advanced workflow management, which includes restricting transitions and customizing the reasons of a transition is not yet possible in the Inheritance model. It is on our backlog to add though.
Also, if you indeed used a high fidelity migration tool and you have a Hosted XML process model, you are stuck on it. You cannot move to the inheritance model as seen in this link.
In summary then. On the Inheritance Process model in VSTS this is not a feature that is available currently but is on the backlog as confirmed by MS. However it is not planned for delivery in the next few months and a year or more from now is more likely.
In my case I also had to add addition fields and a new state on the BUG WIT (Work Item Type). This was accomplished on VSTS by customizing a process which is done by inheriting from one of the standard processes ( Agile, CMMI, Scrum ) which you can then customize.
You can add customized rules to a WIT and you can base a rule on changes to the state.... however the rules seems too limited to restrict transitions and the options to set fields doesn't have the "Reason" field available.
In fact, I came up with a solution! Which I admit is not clean as I would like, but it works.
I created three new fields: "Rules error" (Text single line), "Rules broken" (Text single line) and "Rules activated" (Boolean).
"Rules error" I put it on the main tab so I can see the error and the two others I created a tab named "Useless" in which I put them.
Now, add a rule making the reset:
Name: Reset rules
Condition: The value of equals ==> "Rules activated" ==> true
Action: Clear the value ==> "Rules error"
And then one rule per not wanted transition of states:
Name: State change - Approved to Deployed QA
Condition: A work item state changes from ==> Approved ==> Deployed QA
Action: Make required ==> "Rules broken"
Action: Set the value of ==> "Rules activated" ==> true
Action: Set the value of ==> "Rules error" ==> "Can't change from Approved to Deployed QA"
I know, entering something in the field "Rules broken" breaks this enforcement, but as this functionality doesn't exist, it is the only way I came up with when you don't have access to Hosted XML.
Neither of those things appear to be possible at the moment.
The VSTS process customisation is very different to TFS and is still evolving. #1 seems like something that might be added in a future update. But #2 doesn't seem like it would appear, as Microsoft have relaxed most of the transition rules on all the templates on VSTS by default.
This is currently not possible when using inheritance process.
You can vote for this feature request in the community: Allow specifying state transitions when using inheritance process
It's possible by creating our own custom extensions and creating some rules that disable state changes from one state to another state
I have implemented this for my org but haven't published it online..will do it soon
Here is a workaround for denying any users who are not a member of group "HighLevelManagement" to change state from Approved to Committed for PBI:
Create a new Field Called "Unlocked".
create a new rule to "Hide the Field" when the user is not part of "HighLevelManagement" as below
Create a new rule with action "Make Read Only" set to "State" when
Unlocked is False and workitem change from Approved to Commited as
below:
Now whenever a user from HighLevelManagement wants to change state from Approved to Committed he simply tick Unlocked change state and then tick back Unlocked, that way anyone from outside HighLevelManagement will be restricted to change state from Approved to Committed.

How can i know which object is preventing me from saving?

I'm working on a Microstrategy 8.1.525.151 Client with a Microstrategy Server 8.1. While creating a report i deleted some objects and after that, each time i try create or change any object (report, filter, attribute) i get the same error when i try to Save
The error is
'Cannot save, move or copy this object because it has been changed in the Metadata'
I've tried refreshing the schema both in the client and server, deleted and recreated the objects (it only works on the server but doesn't refresh on the client) and also the menu Administration/Server/Purge Cache Objects
With the exception of the Microstrategy knowledge base (which i cannot access) all i have found is mentions of changing multiple objects, however i don't know which objects may be causing this error if any
Thanks in advance for the help
If you cannot create/save any other object I'm afraid that your metadata are corrupted.
There are some utility provided by MicroStrategy to fix them, but I don't think they still support version 8.1. Your best shot is to try with MicroStrategy tech support.
You are the only one with this problem? other users can modify objects?
The way i used to solve it was to delete all attributes and reports i created since i started having such a problem, (it was easier because it was all in a single folder for attributes and a single folder for reports and i suspect in certain cases also other objects would need deletion) also restarted the intelligence server