In Azure DevOps is possible to #Tag a user in the comments of a work item. Is it possible to query the items to find the work items which have comments which I am tagged in?
Write a query that does a Contains Words on History, then use "#display name"
Use the Work items page and select "Mentioned" from the dropdown.
URL would look like: https://dev.azure.com/*YOURORG*/*YOURPROJECT*/_workitems/mentioned/
Note that this also picks up mentions in other fields such as description, but I find this to be the easiest way.
"Work items" Page
Mentioned" dropdown
Note the number of comments. If there are no comments, then clearly you weren't mentioned in a comment.
Sort by "Mentioned Date". Latest occurrence by default.
You can make a custom query just setting the ID in #RecentMentions like this:
Related
I am trying to create a list item with a multiselect field, according to the m365 spo documentation. It feels like I have tried all possible variations, but I cannot get it to work at all.
Is there any official guide as to the syntax for a multi-select value?
Ok, for whomever bangs their heads against this in the future, the format for the seeds of a multi-lookup field is the following:
Id;Value;#
Where ;# is the separator. You may use # as a wildcard for a value, ending up with the following example where I am adding the related entities with Id 3 and 5 to the seed:
3;#;#5;#
or one single entity:
1;#
or three entities:
2;#;#3;#;#5;#
There seems to be a tiny bit of tolerance on the trailing value, but I did not experiment much with this.
PS: it works, and I am very happy, but dear reader know this: if you feel the need for some eye-bleach after reading this, you are not alone!
We have monorepo, my team responsible for 3 of 20 packages/folder of repository, but sometimes we need to touch others packages/folders.
For reviewing teammates changes every member should add “team_label” for ability to filter by this label or to keep opened several tabs with merge requests for each author/team member.
Preferable could be filtering MRs something like this by one of the author:
author: username1 OR author:username2 OR author:username3
We are using GitLab Enterprise Edition 12.6.2-ee
upd:
discussed in gitlab docs comments and there is no ability to filter merge requests even with advanced search
Advanced Search does currently not have the facets available that you use in the dedicated issue or MR search
https://docs.gitlab.com/ee/user/search/index.html#comment-4776091890
Feature proposal:
https://gitlab.com/gitlab-org/gitlab/issues/7826
To filter merge request and all the other kind of thing you want to search for you can read this guide on how to search with filters:
GitLab Filter Guide
Anyway if you want a quick suggestion you have to go in the "Merge request" section of your sidebar menu. After that, you can see on the upper part of the tables where all the merge request are listed a little search bar that says "Search or filter results..." if you click on that a little dropdown opens up to suggest you how to use the search bar.
To search in a list of all the authors you have to input the following: author: (this will let you see a little dropdown with all the authors) or you can search directly with an author name putting a "#" before his name.
If you want to concatenate more filter criteria you have to put AND or OR as you would do in a SQL query. But anything is well explained in the guide.
Unfortunately to date you can't search merge requests with an OR query - and although gitlab states that successive clauses should be ANDed together a quick test suggests that in fact an arbitrary single clause is applied.
See e.g. https://forum.gitlab.com/t/mr-filtering-by-multiple-authors/33864
I've got a simple repeater that list links to uploaded documents using cms.file. I'm drawing a blank on adjust the ORDER BY based on publish date. I can't find anything here on this, so i apologize if this is a duplicate.
Best practice is to add custom field to page type (in this case cms.file or better create the new one) and set ORDER BY condition to this new field. There are also properties like DocumentModifiedWhen, DocumentCreatedWhen, DocumentCheckedOutWhen you can use.
I'm going to use DocumentModifiedWhen as the ORDER By statement.
There are two fields [DocumentPublishTo] and [DocumentPublishFrom] that you can think of using. These are the two fields which appear at the bottom of each form page by default.
I have built a website (with MODX) where some products are managed and displayed via the articles addon. The products should have a custom ordering but I don't know how to use a template variable for that.
If I enter the name of the TV in the "Sort Field" field nothing is shown at all.
So is it somehow possible to use a TV there?
Or is there another way to achive a custom ordering (note that I need the summary and date fields, so I cant't abuse them for that)?
You can do this by using getResource package. Look at sorbyTV, sortdirTV, sortbyTVType parameters in manual:
http://rtfm.modx.com/extras/revo/getresources#getResources-SelectionProperties
Currently, the site search will search all of the skus of the items marked as being visible in search. This is all well and good.
The problem arises when the customer knows a sku of the individual child item. So, let's say a product comes in both a 20 foot and 25 foot variation. We would put those into a configurable product and have a single product page where a customer could then choose which of those two lengths.
What happens is, a customer invariably knows that the sku of the 20 ft variation is RDB-20, while the other is RDB-25. A search for RDB-25 then, comes back with no results since the simple product is not visible in search - it doesn't realize there is a match.
How do I get the search to search an item with visibility "Not Visible Individually", when it's parent is visible in search?
The desired effect is that, if a child SKU is searched for, the parent should show up in the results.
There really is no good way of doing it without extending the default search, but at that point you might as well look for other options.
Here's a workaround that might be doable depending on how you manage your products and it worked for me until I moved on from the default search.
Rather than altering the search, try adding an attribute to all products and make it hidden concatenating all the skus into this field. The search should find the text attribute and show the configurable.
Its a bit of a workaround but works for me.
This is untested, but I did a bit of perusing in our attributes and I think I found something that might help.
Currently since our child products don't show up in our search, we have the parent populate with the children product's attributes.
However, things like brand, taxable amount, description, populate for every child product while our SKU does not.
The only difference I can see between the two attributes is under manage attributes -> click on attribute -> and then under properties go to frontend properties and select
Use In Search Results Layered Navigation: YES
Used in Product Listing: YES
Use In Layered Navigation: Filterable (with results)
I'm not sure which of these do what, but in the population of the fulltext search data table, somewhere it is being told to populate for the children and I believe that the admin panel is where.
I hope this helps!