I am aware that JIRA dataset is in beta stage right now in Data factory. But still is there any way to pull the custom fields data?
Right now when i am copying JIRA issues data it is giving me only the standard fields present in any of the Issue.
I want custom fields too. Any way?
So through hit and trial, i got to know that tables that starts with 'Extras- ' are the ones which has custom fields and that too masked. Again through hit and trial I figured which field value I wanted to extract.
You can try the advanced tab.
For linked service:
advanced tab for linked service
For dataset:
advanced tab for dataset
Related
We have two fields Fix Versions and Affects Version in a bug wherein the drop down values are to be auto populated based on the tags created in Azure Repos. For ex: if there are tags v1.001.560, v1.001.561 etc and for any new tags created, the tag version should appear as a drop down value for these fields. Is there a feasible approach to achieve this? Please suggest.
In short, there is no method to meet your needs now. As a suggestion, you could submit a suggestion ticket to suggest the feature on: https://developercommunity.visualstudio.com/report?space=21&entry=suggestion. That will allow you to directly interact with the appropriate product group, and makes it more convenient for the product group to collect and categorize your suggestions.
DevOps only supports setting to specific values for your custom picklist fields. Please note custom field is used to support tracking data requirements you have that aren't met with the existing set of fields.
Besides, to realize your idea, we should auto populate tag values to the field when opening the work item. However, we also not have such a trigger even though getting the tags with Rest API.
I'm looking to migrate a project from one org to another in Azure DevOps. We've ended up with two or three orgs, and this project that I'm looking to move has all sorts of weird and wonderful work items created and custom fields added. What I'm looking to do is move the project and then see if I can persuade the powers that be that certain things can be dropped but I have an immediate need to move as-is so that reporting and other work isn't impacted.
I have tried to get this to work with the migration tools (and tried to follow the videos) but have hit a dead-end. I think there are two issues potentially. One being the ReflectedWorkItemId. It says that it's not found in User Stories but I'm not sure how to resolve this? Do I go into user stories and add a field called 'ReflectedWorkItemId' and populate it with the work item number and/or add the same field in the destination org process?
It also mentions in the info that it can't find one of the Work Item Types - Processes. There are a few other custom work item types that have been created too but I assume it's given up on the first one. Do I have to create all of the work item types and the custom fields for each work item type in the destination org? Or am I getting the wrong end of the stick with this?
To provide sync as well as migration it is important that the tools knows which items have already been migrated. This is the purpose of the ReflectedWorkItemId field.
The field is not required in either case, however... if you don't have
the field then the system cant be re-run as it will re-copy all
completed work items. If you add the field to the target then it will
only copy those items it cant find. If you add the field to the source
(yes it needs to be the same refname), and set UpdateSoureReflectedId
to true then you can also filter the source, using a query and limit
what you load.
The former prevents duplicates, and the latter allows you to filter
the data load...
This is mentioned in this document. Here is a similar issue you can refer to.
TF201077 that usually happens when the target Project does not have a work item of that name. You can refer to this issue on github for help.
We've added and enforced a "Summary" field to our PBIs and bugs in Azure DevOps, this is so work performed can be described in non-technical terms. We'd like a simple way to collect the summary field from DevOps for a specific branch. Is something like this possible?
I tried creating a view within Azure DevOps but was unable to select the "Summary" field. Therefore when viewing the data through Power BI desktop I could not see the information we're trying to retrieve.
You can't add fields with a data type of Plain Text (long text) or HTML (rich-text). These fields aren't available from Analytics for the purposes of reporting.
https://learn.microsoft.com/en-us/azure/devops/report/powerbi/analytics-views-create?view=azure-devops#3-select-the-fields-to-appear-in-the-report
It seems that you want the custom summary field in the bug work item to be displayed in the PBI.
To do this ,you can create a custom Analytics view to define the filtered set of data, and then load the view using the Power BI Data Connector.
You can select the custom field to appear in the report in the Fields tab of New View dialog.
For details guide , please refer to this document.
I want to create a query with my followed works items in TFS 2017, but I didn't find the field name for the followed state.
I want to create that query in order to add a new widget in home dashboard.
Is it possible to make a query with your followed items in TFS2017?
No, there isn’t the feature to create a query with followed work items in TFS or VSTS and pin to dashboard. You just can check followed work items from Work>Queries.
I submit a user voice here (Query for followed workitem and pin to dashboard), you can vote it.
You can achieve this scenario by creating a custom Followed work items query (System.ID In #Follows) and saving it to Shared Queries. Then, simply pin the query to your dashboard as a Query Results Widget and anyone who views it will see their followed work items (similarly you can pin an Assigned to me query using the #me macro and users will see items assigned to them).
The #Follows macro has been around in VSTS for awhile and was introduced in TFS 2017. Check out our documentation on queries macros for more information.
As proposed by Lauren, in TFS 2017, you can build an ad-hoc query "ID In #follows" (Field=ID / Operator=In / Value=#follows). The results will be similar to the Default Query "Followed work items" under Work>Queries.
However, I was never able to save this query: trying to save always got me an error "TF212023: You cannot compare fields with different data types in the WHERE clause of a work item query. The error is caused by «[System.Id] in (#follows)»."
What I found out is, that the query works well in the web interface, but cannot be run nor created or edited in Visual Studio.
I did not even find a way to "follow" a workitem in VS, this seems to be available only in the web interface as well.
Hi I need to add Custom User Field (Dropdown) in Moodle. I know I can add it through https://docs.moodle.org/24/en/User_profile_fields and https://docs.moodle.org/dev/User_profile_fields
I went ahead with above method and added dropdown accordingly. However, when I see it in database, {user_info_field} it shows only one row with my select fields seperated by new line. Screenshot is listed.
I want these params to be appear in separate rows. Because, I've few development in pipeline which involves creation of custom invoicing plugin that allows to store pricing for each university.
That is how dropdown fields store their options in Moodle - all the values, separated by newlines.
If you want a list of possible values, retrieve mdl_user_info_field.param1 then use explode("\n", $fieldvalue).
I Used in built cohort system to categorized users in different University. Here I didn't have to create custom profile field.
For invoicing plugin, I will manipulate same cohorts (in my case University) by creating local plugin which adds tables to database field. Thank you all for your help.