when I make a call to JIRA API the response contain a large number of custom field with different IDs.
It's possible resolve it directly into API response?
I just try to call api on /rest/api/2/field to obtain all jira custom fields, but after that I should do a manual mapping script, it's soo annoing. There is a solution for this problem?
In the next time I need to export, for every issue, antire activity, attacchments and comments to store in external archive that can be consult in future.
Related
Is there a way to find out if there was any delete entity call to a azure table in last 'N' minutes? Basically my goal is to find all operations that updated the table in last 'N' minutes.
Update: I am looking for a way to do it with a rest api call for a specific table in the storage.
If using Azure Portal an option, you can find this information via Metrics. For example, see the screenshot below
]
Basically here I am taking a sum of all transactions against my table storage where API call was DeleteEntity.
You can find more information about it here: https://learn.microsoft.com/en-us/azure/storage/common/storage-metrics-in-azure-monitor?toc=%2fazure%2fstorage%2fblobs%2ftoc.json.
UPDATE
If you wish to get this information programmatically, I believe you will need to use Azure Monitoring REST API. I looked up the request sent by Portal and it is sending a request to /subscriptions/<my-subscription-id>/resourceGroups/<my-resource-group>/providers/Microsoft.Storage/storageAccounts/<my-storage-account>/tableServices/default/providers/Microsoft.Insights/metrics/Transactions endpoint.
UPDATE 2
For a specific table, the only option I can think of is to fetch the data from Storage Analytics Logs which is stored in $logs blob container and then parse the CSV file manually. You may find these links helpful:
https://learn.microsoft.com/en-us/rest/api/storageservices/storage-analytics-log-format
https://learn.microsoft.com/en-us/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages#logged-operations
Is there a way to get ALL the responses for a single day in one transaction for a specific survey? on the API doc, I know there is the /surveys/{id}/responses/bulk option, and even I can send the start_created_at variable.
But I think that the API response has a max number of records/data it can send, it that case, what could the solution be? Paging through the results?
I'm using the .net API, found at this site, but I can build my own wrapper if necessary.
Reference link to API doc: /Surveys/SURVEY_ID/responses/bulk
Yes you're right the /surveys/{id}/responses/bulk endpoint is what you're looking for, and you can use the start_created_at and end_created_at to filter data to a date range.
The SurveyMonkey API doesn't allow a full dump of all your data, it will always be paginated. By default it'll paginate 50 at a time, but you can change that by using the per_page GET parameter.
That max per_page varies by endpoint, for responses BULK it is 100. So you'll have to fetch 100 at a time, looping through the pages to get all your data.
One alternative is to use webhooks and set up a subscriber, that way you can get new responses in real time and fetch them one by one. That way you can keep your data updated on your side as new responses come in, rather than running a script or endpoint to bulk dump all your data. But this depends on your use case, if you're building something like an export feature, then you'll have to go through the paginated route.
I was wondering if there is a way to update a custom field during a workflow transition in JIRA.
The "Update Issue Field" post function is the closest feature I found, but its document explicitly states "This post function cannot update custom fields and must be positioned after the other optional post functions."
I was wondering if there is another function can support my purpose.
JIRA Suite Utilities is the standard add-on everyone uses to do this
https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Post-Functions#JIRASuiteUtilitiesWorkflowPost-Functions-UpdateIssueCustomFieldPost-Function
Not available for OnDemand
EDIT: JIRA Suite Utilities is now available for JIRA Cloud and comes pre-installed in new Cloud instances.
EDIT: And now it is no longer free.
There is a Post Function Update Issue Custom Field now in JIRA OnDemand 7.1. It seems to be pretty limited, e.g. you can't write an expression such as setting the value if it's currently empty.
I'd provide a link to their documentation page but their search claims it doesn't exist.
There is possible to execute Groovy script as Post Function and it let you do almost everything.
For example, here is script, how to update custom field (option) dependent on value of another custom field value.
EDIT: This solution is abel only for hosted instace. Not for Cloud
In Google Analytics a web-property may hold more than a single profile, in which case one of them is suppose to be defined as the default one (in GA you browse inside it you can see a [DEFAULT] tag by its name).
Using the Legato gem, is there a way of querying whether the profile is the default one or not? is there a way to pass parameters to add this information to the request?
Unfortunately, this appears to be an API limitation.
Browsing the developer reference for the API v3, the profile representation contains no property indicating its status among siblings.
I am looking for a simple way to get data displayed in an issue as just plain text. Basically, I want to be able to type in a lookup id in the issue creation and then once the issue is created, it would call one of our web services to retrieve data connected with that ID.
This wouldn't be coming from another issue tracker, but rather straight from one of my databases.
What would be the easiest way of accomplishing this? I would like the workflow to be: Enter id #, hit save, see the data with that ID displayed in the ticket (Doesn't need to be editable, just displayed in the ticket view).
The easiest way is to create a workflow function that is triggered at Create transition to do the job. There your code can query information from the database and replicate them into JIRA standard and custom fields of the issue itself.
Then you can prevent edition of replicated fields by tuning Edit screen for your issues.
You can also use your function to update field content from time to time, either at transition or in a trigger.
An option is to create some read-only custom fields than query each piece information from the database. It will prevent data replication but it will be probably slow and it does not apply to default fields.