Is it possible to import/ upload bugs along with linked tests (by id/ name) in Azure devops?
The microsoft docs (https://learn.microsoft.com/en-us/azure/devops/boards/queries/import-work-items-from-csv?view=azure-devops) mention about importing work ites with parent - child relationship. I need to import bug and associate it with test case id/ name (direct link relationship). E.g. In csv file I can mention bug title in one column and associated test case id/ name in other. Then I should be able to upload csv file, and test case should be automatically linked to bug after upload.
As I know this feature is not supported yet. We can't import bug and associate it with test case id/ name (direct link relationship) from csv file.
When creating Query, no field in filter can match the direct linked work item. Also, Exporting to csv option doesn't support this, see:
As an alternative way, I suggest you can post a feature request here in our DC forum(user voice forum). If it get enough points, the team would consider it seriously. Hope it helps :)
If you have linked the bugs/tests with work Item , it can be exported as a CSV, you can read about more here.
I have suggested a feature with MSFT
https://developercommunity.visualstudio.com/idea/952141/import-upload-bugs-along-with-linked-tests-by-id-n.html.
Please vote if you find it useful.
Related
I am building an integration for a client with the HelloWorks API. This is a service that allows you to create user-fillable PDF forms.
It appears that their product supports formatted/template strings/formula fields as outputs to the PDF files, as when
I create a Date field, it creates an output field with the following data:
#{format(:date, #field_XXXXX, "{0M}/{0D}/{YYYY}")}
However, I cannot find any kind of documentation as to what is the format of this template string/formula field.
In case anyone is still looking for an answer for this, this is what HelloWorks support team has to say.
As for documentation for the format, we do not have any documentation for that at this time and the ability to make those edits are going to be depreciated in the future as our product team wants to bring those capabilities to the portal without custom edits.
I've been looking for any documentation which suggests whether there is a way of saving Document Settings & CustomProperties such that they're automatically propagated to co-authors of the current document.
I've done some testing which suggests that's these settings aren't automatically propagated even when the document is saved. I'm also storing XML inside the document so I'm concerned that this won't be propagated as well. Since I'm doing this in Excel, I could always create a hidden sheet to store the properties in and have a watch on the table (or some similar set-up) but this isn't really the avenue I want to go down since some user could easily come along and delete the hidden sheet or manipulate its contents.
Has anyone come across this issue and managed to find a solution to it?
Welcome to Excel JS world.
I have verified this issue, it looks like a co-auth bug in settings and custom properties API. We have created 2 bugs (BUG 4173957 and BUG 4173952) for tracking this issue.
As a workaround, you could use our beta API worksheet custom properties, which is in preview, this API support co-auth. You could try it out, please let me know if you have any suggestion on this API. thanks.
In some 'old' lotus notes applications, we created a history of each document: who created the doc, every person which edited it + the respective dates. The code contained several libraries in lotusScript.
For xpages, is there any snippet / sample working example which I could use? I found this but I couldn't download any example ...
ValueChangeListeners allow you to capture changes to specific components. I've used them to create audit trails in customer applications before.
Tony McGuckin has an XSnippet for it:
http://openntf.org/XSnippets.nsf/snippet.xsp?id=server-side-value-change-events-listeners
Declan Lynch covered it in a blog post:
http://www.qtzar.com/using-a-valuechangelistener-to-build-an-audit-trail/
Don McNally has also done a blog post:
http://dmcnally.blogspot.co.uk/2013/02/xpages-detecting-and-logging-field.html
I don't know of any pre-done snippet yet. But this becomes a lot easier in XPages especially if expand into Java. When I create an application these days I basically convert the document to a Java object. I don't do this yet but it would be easy to store in the object a Map of all the fields and their current values and then on save, look for differences and then write them out to a log document.
this could be done without java of course. Create an map object in scope. Populate it on loading of the document and on save do the compare and write.
Something went wrong with that project on OpenNTF (don't ever use an ampersand in the name). I'm the original author of that custom control. AFter some digging I found a direct url to the project here.
I noticed that sitecore has the option of exporting users in an Excel format.
I need to have similar functionality for exporting 'participations', (a users can enlist to take part in an 'event', and if their entry is approved via a sitecore workflow, a 'participation' item is created in the content tree)
Since mostly everything in Sitecore is in essence based on items, and I want to export items to Excel, my question is - what are some of the best ways of doing this?
Questions:
Is there a way to re-use this functionality for regular items?
Would it be a good idea to create a custom admin page (any tips on doing this?) which has some custom code that reads the items from the database using the API?
are there sitecore plugins/shared source projects that can help me achieve this?
Or does anyone have a better idea? - would it be better to just store the participations in SQL? I'm mostly doing it this way because I want to make use of the 'free' functionality offers, for example workflow, but if that leads to me using anti-patterns please shoot me ;)
Link is different now: https://marketplace.sitecore.net/en/Modules/Advanced_System_Reporter.aspx
P.S. Couldn't leave a comment to original answer as I don't have enough reputation. Oh well :)
Found a most excellent shared source module which does exactly this (and much more)!
Basically it allows you to configure (and easily extend, if you need to) any kind of table based report on 'items'.
The report module shows up as an application in the sitecore menu (like the user manager tool) and comes with features such as xml,csv, xls export. It's also really easy to set up, once you get the hang of it.
http://trac.sitecore.net/AdvancedSystemReporter
I'm trying to use SQL, REST or the Jira Api to find out what the velocity of a project is at any current moment in time. Right now I am trying to find the total number of story points assigned/completed for each sprint and version and from this calculate the velocity of the overall project.
The problem is that Greenhopper is an addon to Jira and does not change the Jira database in anyway, so it must store this information about scrum/agile projects elsewhere. Any ideas where this information might be located?
Thank you!
I finally worked it out!
So here is some of the techniques that we use to access data from Jira.
SQL
This SQL statement for example counts all the issues from every point in Jira for each priority.
SELECT
project.ID AS id,
project.pkey,
project.pname AS projectname,
jiraissue.PRIORITY AS priority,
COUNT(*) AS total
FROM jiraissue
LEFT JOIN project ON jiraissue.PROJECT=project.ID
GROUP BY project.ID,jiraissue.PRIORITY
ORDER BY project.id
Also check out... http://confluence.atlassian.com/display/JIRA041/Example+SQL+queries+for+JIRA
REST Api
I have not tried this properly but there is also a set of REST api that you can use to access some of the data from Jira. This documentation is available here: http://docs.atlassian.com/jira/REST/latest/
An example link: https://JIRA_LINK/rest/auth/1/session
Java
Also another useful link for JIRA Java api: http://docs.atlassian.com/software/jira/docs/api/latest/
I use an older version of jira & greenhopper.... but in that version, greenhopper allows you to choose the field you "burndown" by. In my case it's a field (i believe a custom field) called "Likely". So it should be there in the DB/API somewhere. good luck.