I'm trying to create a filter to find a missing task in several Workfront plans. I have tried system filters with no luck.
I can filter if missing a field but not a task.
I am using the web interface. I am looking for a task with a specific name (i.e. Identify External Resources), that should be in multiple project plans, and I want to find plans without that task listed.
Your requirements are:
Find all projects
Filter for projects that do not contain the task 'identify external resources'
My assumptions are:
You want ALL projects that don't contain the named task
Your criteria is that the project either has the task or doesn't (you don't care if has 1 task of that name or 100)
The solution is:
Create a project-level report
Go into the filter tab
Switch to text mode and add the following:
tasks:name=identify external resources
tasks:name_Mod=cinotcontains
This will find all projects that don't have a task named 'identify external resources'. You can combine this with additional filter to add other tasks and/or status filters.
Related
How can we add calculated custom fields on a process in Azure DevOps Boards. Is there any extensions that can be used for creating a Calculated custom field?
Azure DevOps support rollups in the backlogs only: Display rollup progress or totals.
To use your own logic, you can:
Create an extension (for example WSJF (Weighted Shortest Job First)).
Use az boards work-item to get, calculate, and update fields.
Use Excel to create calculated columns and publish fields: Bulk add or modify work items with Excel
If you mean creating a custom field Calculated to your project process. You can follow below steps.
1, Go to organization settings -->Process-->Select the process which your project is currently using.
If your project is using the System processes: Agile, Basic, Scrum, and CMMI. You need to create Inherited processes. For System processes are locked from being changed. See System versus inherited processes.
After you select your project process. You can select work item types to add the custom field. See Add a custom field.
2, If your project was using System processes. After you created the Inherited process, and added the custom field. You need to change your project process to this newly created inherited process. See Change the project process.
We have 100+ services/apps in a repository in Azure Devops. We have defined a single CI/CD YAML multistage pipeline for each (build and deployment). This limits blast radius and allows for auditability of each release of each project. We rely on templates for all the real pipeline work so this is easy to maintain; just a small root azure-pipelines.yml file for each project that includes the needed templates.
Now, we'd like to start using PR validation builds. And, as best as I can tell, we have two options:
Create a separate PR build for for every project and use the UI/API for policies to create 100+ policies
Create a single PR build that has stages for all 100+ projects.
I'm not a fan of the 1st option as now we'll have 200+ builds. The 2nd option is possible, but to avoid a 3 hour PR build, we'd need a way to only run needed stages (aka project builds).
Is there a 3rd option I'm missing? If the 2nd option is our best bet, how do we turn off stages for projects not changed in that PR (i.e. what condition would we use)?
(FYI, our policy is to change only one project per PR, but there are, on occasion exceptions to that.)
For personal suggestion, I also recommend the second method. Though the build script would be very large in one configure file, but much better than have hundreds build configuration files.
But the difficulty is these 100+ apps are all in one repository. This means all the normal method will not suitable for you, include using Build.Repository.Name value as the stage condition. Also, there's no more details which describing the source file path stored in the commit.
So, I suggest you and your team developers input the project name info into your commit message. Then, in the build pipeline you could use the variable Build.SourceVersionMessage to get its comment message. Since this is a environment variable which only work in step level(Not work for stage level and the job level), it needs you add one task in the first step and use the condition for it.
The logic of it is add one step as the first one in every stages. This step is only used to conditional judgment. If the Build.SourceVersionMessage matches the prefix or any key contents words, the jobs will be early-exit.
If use the condition like this:
condition: startsWith(variables['Build.SourceVersionMessage'], '[maven-plugin]')
It needs your commit message must follow a strict content writing format, starting with the specified project name.
Another condition can for you consider is:
condition: in(variables['Build.SourceVersionMessage'], 'maven-plugin')
This does not need the strict content writing format, but also need input the project name in the commit message. Thus it could be evaluated in the job condition with the above script.
Hope it could give you some help.
I have more than 35 projects in an organization in Azure DevOps. These are the solutions of a Single product. Right now I am creating build and release pipelines for each project one by one.
If I create a pipeline for a single project and release the build, I want devops to create pipeline & releases builds for all the other projects(in the same organization) together at once.
For eg, There are projects A,B,C & D. If I create a release pipeline for Project A, will Devops automatically Release build for other projects "B,C & D" in the same organization at the same time.
We need to avoid creating pipelines for each projects one by one. Is this possible and is there any scripting or configuration to achieve this?
Thanks in Advance.
The process of setting up multiple release definitions with the exact same tasks can be very time consuming and difficult to manage -- fortunately, our team solved this problem using Task Groups!
Task Groups allow you to bundle multiple steps into a single "group", parameterize them, and then invoke them like a single step. You can also edit the Task Group at any time which will cascade to all places where it's used.
The other consideration is that you can bundle your custom variables into Variable Groups and reuse them between Release Definitions. Having your configuration reusable also has the benefit of only having to edit a single item.
I'd recommend:
Create a single release definition as a golden reference example.
Add your build steps for a single stage/environment
Once you're happy with this release definition, multi-select the steps you want to bundle into a group, open the context menu and select the option to convert to a Task Group. This will remove the steps from your release and move them to the Task Group.
Customize the Task Group with the appropriate parameters and then save it.
Modify your release definition to use the Task group parameters.
Add the additional stages to your environment, and add your custom Task Group to each parameterizing with configuration specific to the environment.
Once you're happy with the Release Definition -- use the Clone feature to create 34 more instances.
The same approach can be applied to builds.
I have a Task Group that I created out of a set of build tasks. I am able to edit the tasks quite well, but i now realise i will need to add another parameter to the task group. How do I go about doing that?
Task group parameters are automatically created based on the variables used in the tasks. If you reference a new variable in a task that's within a task group, it will pop up.
In addition to the accepted answer, if you want to add parameters that are not directly referenced by tasks within the tasks group (e.g. to use in a config file token replacement task) then you can export your task group, edit the .json file then import it back in. The parameters are in an inputs array near the end of file. You can also hide parameters here if you only want to use them internally to the task group by setting a default value and adding a 'visibleRule' property, see this article for details: https://medium.com/objectsharp/how-to-hide-a-task-group-parameter-b95f7c85870c
This will create a new task group rather than updating your current task group. If you want to update the task group, you can use this REST API:
https://learn.microsoft.com/en-us/rest/api/azure/devops/distributedtask/taskgroups/update?view=azure-devops-rest-5.1
I need to assign a task to many groups in a alfresco worflow!Can anybody help me with a example?How to modify a model and share-workflow-form-config.xml to suport this option?Thank you in advence!
One way of achieving this is as below.
Alfresco supports concept of group inside group(subgroups).So you can assign task to that particular group and achieve your requirement.
Further more,for creating workflow there are 2 workflow engines which are widely used(activiti and jbpm).You can use any of them.
For creating workflow you will need to create below files.
Task Model(Defining Properties)
Process Definition(Defines Workflow)
Web Client configuration(Displaying properties in UI.It defines forms)
Context File(For injecting process definition and model file)
For more details on JBPM workflow you can find below link use full.
http://krutikjayswal-alfresco.blogspot.in/2014/04/jbpm-workflow-in-alfresco.html
In above blog, for activiti workflow change will be only in process definition file.