When I submit an Attachment to the Azure DevOps REST service (create), is there a place I can go to visualise all of the attachments in there? Or is my best course of action to just send a GET which will give me the list?
My problem then becomes...that there is no way for me to delete unwanted attachments.
Is there a place I can go to visualise all of the attachments in
there? Or is my best course of action to just send a GET which will
give me the list?
Yes, the best course of action to view these attachments is to send a GET request.
In fact, after you upload the attachments to a work item via the API, all of them are managed by the backend. The backend does not assign any relevant info to the work item. This leads to the situation where you cannot view them from the UI, unfortunately.
Microsoft hasn't expanded the API/SDK to provide an "attachment delete" call yet.
You can also press F12, then try with uploading and deleting attachments from one workitem within the UI.
As you can see, the attachments deleted are run by the backend via sending an event call. In your scenario, you cannot remove those unwanted attachments until now.
You are not the first one who has requested this feature. See this suggestion: Unable to delete/remove attachment from work item by using VSTS api. You can vote and comment there to raise its priority. The product team can then consider adding the feature to the roadmap.
Related
We currently migrating our .Net Application from EWS to Graph API using msgraph-sdk-dotnet
Primarily we are using message-delta Requests to observe mail folders in order to detect incoming mails. So far so good.
Migrating from EWS
When using EWS we were able to detect moved mail events/actions and to distinguish these mails from new incoming (new sent) mails. So far, we didn't figure out who this can be achieved by using MS Graph API.
About use cases
There are use cases where we must distinguish a newly sent email from a Mail which has been moved/dragged from another folder into the observed one manually by any user (via Outlook). This use case scenario includes the following flow: Let's say the inbox is the observed folder, a new incoming mail has been sent to the mailbox and the mail has been detected by our delta request observer.
Then the user decides to move this mail into another custom but not observed folder using Outlook. Finally, the user decides to drag this mail back into the observed folder. Now we'd like to have a solid strategy at hand to detect this mail as moved (not as sent or updated, we need to distinguish these states).
Hint: This flow demonstrates why we can't really rely on isRead: Users can use a client (e. g. Outlook) to mark an any mail as read, which is most likely the case when you drag a mail from folder to folder.
How to detected a moved mail?
Are there any properties from Mail Resource which can be used to identify if a mail has been moved specifically? Maybe something not mentioned in the public API documentation (ODATA, something which can be extracted by folderIds etc.?) or something which is supported by beta API version? Any ideas?
We also investigated the subscription resource but did not find a specific changeType which specifically reflected a moved mail.
How should we resolve these issues? Any ideas how to develop a solid detection strategy for moved mails using Graph API?
Thx for any hint, advice or help you can give
I have started looking at the lastModifiedDateTime property. It appears that when the message is first received, the lastModifiedDateTime is 1-2 seconds after the receivedDateTime. When the message is moved to another mail folder, receivedDateTime stays constant, but obviously the lastModifiedDateTime changes. I am still looking at the Microsoft docs to find everywhere the lastModifiedDateTime property is changed.
In our team we simply want to link to existing e-mails. I see many explanations online on how to make an automated procedure that triggers when an e-mail comes in, but that's not what we want.
We simply want to link to an e-mail in our inbox in the work item.
Something like 'Refers to: 'e-mail'' .
Unfortunatelly, it's not supported to link work items with existing emails.
Link types: https://learn.microsoft.com/en-us/azure/devops/boards/queries/link-type-reference?view=azure-devops
You may add the links of emails to Description as a workaround.
In addition, you could add a custom field to support tracking data requirements you have that aren't met with the existing set of fields. Please refer to this document: https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/add-custom-field?view=azure-devops
We're trying to automate when UserStories are resolved in Azure Devops, the attached video on the UserStory gets posted as a New Yammer Post where the contents includes the Title of the UserStory and the video is saved as an attachment to the post. This helps our company keep up to date with new functionality added to the system, to try and keep everyone updated with developments each build.
Since this feature does not supported by service hook or other UI of Azure Devops.
You can try with one third-party website Zappier, and try with Post Yammer messages for updated Visual Studio Online work items.
After click Try it, you will be direct to the page that need you specified the org and Yammer account. Please follow the page step to configure it.
After configure it, please edit the message which you want to achieve:
And then, according to your demand to specified the configuration of Azure Devops and Yammer event condition:
This is a 2 part issue:
How to move/delete a file after processing. Currently we can only copy, but the original file remains in the source. Ideally we don't want to add a separate process to get metadata and compare if processed or not. I have been following one blog that asks to use a WEB activity and the Delete Rest API. I have gotten to that point, but I am not able to understand/follow instructions on to obtain the ACCESS TOKEN. It shows Curl steps, if someone can help on this would be great.
I have created a pipeline, that has 4 Main activities. As part of this pipeline I want to be able to send email notifications for Success and failure.
Each success of an activity moves to the next activity, but if any activity fails it will send email. I Want to be able to have one SUCCESS or FAILURE Notification and dynamically add content to email instead of sending email on previous activity. For Failure it seems like I have to create a separate web activity for each activity to align a Failure, which is not elegant.
Based on how the WEB activity is set to use the logical apps for email, we have to define the activity name that the email is associated with (at least based on my understanding). So i created a separate WEB activity for each failure email, not very elegant.
Does anyone have a better way to handle.
enter image description here
enter image description here
The only alternative is using a logic app to delete blobs, you can trigger the logic app also via a Web activity. Can you share the blog URL for the delete via web?
As for the email on failure, the issue is that you cannot have 'or' dependencies in the pipeline. A workaround that I'm using is to introduce a variable, when an activity fails or when the pipeline is finished, it sets the variable. In parallel in the pipeline I have a while activity that checks this variable. When it gets a certain value an action will be triggered. Also not elegant, but you don't need a lot of Web activities this way.
Is there a configuration change that can be made to Trac to send a notification to an email address only upon the creation of all new tickets? If it can't be done through config, a plugin would be the second best option, with source code modification as a last resort.
NOTE: The setting smtp_always_cc in the notification section of TracIni will send messages on all updates. I'm in need of email notifications only on the creation of a new ticket.
Does this have to be an email notification? One option you have is to create a query that will list the ten (or however many) most recently-created tickets. When looking at the results of the query, use the "RSS Feed" button at the bottom of the page to subscribe to a feed that will notify you whenever the results of that query get updated.
You could write your own ticket listener plugin (or rather, override the default one and tweak it), or write a email filter (procmail?) to remove non-creation mails.
The smtp_always_cc configuration option in trac.ini will do exactly that.
The one caveat is that it will also send an email on any updates to that issue -- not only on issue creation. This may or may not be what you want. See the TracNotification page in the help wiki for more information.
We use this feature in our product at Akiri Solutions.