We use VSTS/Azure DevOps at work, and have recently updated all our README's and wiki's in our company to improve life for new starters and team switchers, and for general quality of life.
I've just noticed that the [[_TOC_]] table of contents element is suddenly very janky - only a few links work, whereas it linked beautifully a few weeks ago. IT still creates the table, but the table is pretty useless if only 10% of the items actually go to the expected view when you click on them.
Does anyone know what caused this, and if there's a fix? Should I raise a bug with Azure?
Thanks!
Related
I'd like to retrieve the number of closed issues in a repository.
With GET /search/issues?q=repo:tidyverse/dplyr+type:issue+state:closed I obtain:
total_count 3322
incomplete_results false
However here I can read that there are 3334 closed issue at the moment:
Why is there a difference of 12?
I've contacted GitHub support and they triggered a manual reindexing of the issues in this repository, so the search results are now consistent.
However they said that it can happen again:
Unfortunately this isn't a trivial issue, and although our engineering team are continuing to investigate this - we don't have a timeline on this being 100% resolved, 100% of the time.
I use Query Result tiles in my dashboard to help teammates on multiple projects to quickly view the work that is assigned to them. We used to be able to click on a given task to open the detailed description of said task but now it no longer works. The tile only shows the associated user story and is no longer linking to the detailed view screen.
I have checked the queries used (simple work items and direct link query that shows all tasks assigned to a given user and its associated User Story) and reviewed the latest updates to Azure Devops but I can't find any changes that could affect the expected results.
Sorry about this issue you meet. This is caused by our server. There are some mistake occurred on our side, so that the work item which displayed on dashboards could not be clickable successfully now.
You can follow this ticket which report on Developer Community.
The fixed release has been deployed now, but haven't cover all regions. It may take some time to finish that. Please wait for this fix deploy finished. And if you still have this issue recently, you can vote and comment on Develop Community.
Our product engineers are still focusing on this issue and will help you investigate more.
I'm begining work with wit.api chatbot and conducting through their quickstart example. It looks very simple and clear. But it only looks. I can not even create second branch with "missingLocation", becouse I get
"Conflicts with "The weather is {forecast}"
It's conflict between two branches. I have looked documentation and almost everything found in google. But I have found nothing about story conflicts and how treat them.
I will be very gratefull for any tips or references in this question.
I've had this happen occasionally - it's annoying but usually fixes itself after saving and refreshing your stories page or clearing out any unused actions. It can take a couple of tries then it will go green and work all of a sudden.
The google dat.gui is a great little interface. http://workshop.chromeexperiments.com/examples/gui/#1--Basic-Usage
I really want to use this on a new project, but it doesn't work properly on touch screen devices.
However, since they migrated it from Github to code.google.com, things seems to have stalled and issues are going unfixed.
Being brutally honest, I think the project would have more community contribution if it were back on Github. Could I fork it and create my own version, called something like dat.gui MkII, and encourage people to contribute to my version on github? The problem however, is I don't want things to get diluted and create confusion. Would it be better just to completely rebrand it away from dat.gui, and say it was originally forked from there?
Apply a
Cost–benefit analysis
to forking the project.
Cost
forking could dilute the project and create confusion
Benefit
could renew interest in the project and result in more issues being fixed
In my opinion it is worth it, you could alleviate some confusion by having a detailed README on your homepage decribing the situation and/or linking here.
I have started to use Cloud9 IDE recently and have to say I really like it as an individual. I use VS 2010 at work and TFS 2010 too. This made me think about the TFS equivalent for Cloud9. GitHub is something I have always been aware of but never really used.
I have done my research and read docs etc, what I really need some clarification in though is the whole Work Item system. I know GitHub has an Issue tracking but does it have a Work Item system similar to TFS. With the main features such as assigning work items to developers?
A little explanation to just clarify would be fantastic. Thanks!
If you're looking for a way to have Issues show up like WorkItems in your task list in visual studio, I don't think there is a solution for this to date.
You can however assign developers to issues within GitHub:
Create or Edit an Issue
Click the gear next to "No one is assigned".
Select a member from your organization to assign the issue to them.