I created a task on jira (agile) by using kanban board but, I couldn't move it to "in progress" column. Finally I found the solution. You can see the problem and the solution step by step via pictures.
The problem is this:
Follow the topic to find the solution.
Just follow the steps. if you know a better solution, please share it.
The solution is:
Go to administration panel, open integrity checker, select all and click to Check.
Select Fix all and click Fix.
You'll see the fixed issues. Then click OK.
Finally you can do anything with your task again.
Now follow the pictures.
step 1
step 2
step 3
step 4
Please note that the usual reason for this problem is that the Conditions in the workflow are incorrect and the user does not match the rules set by them.
The problem answered by the main answer here only applies when you have corrupted data.
It also neglects the fact that you should treat corrupted data as a potential problem that you should investigate - it will be caused by crashes, or broken add-ons or scripts and you should track them down and fix them.
Related
long time listener, first time caller!
I've spent two days searching for an answer to this so hopefully someone here may be able to help.
I've set up a personal/free VSTS instance and created a project.
One of the first tasks I want to do is setup the build pipeline, so create a new pipeline, define the agent pool as VS2017, connect to my Github repo etc, all of which is fine.
Next I try to add an Agent Job, again choosing VS2017 as the agent. With no other options chosen, if I try to save the build definition I get the following error message (and cannot save it);
The AllowScriptsAuthAccess build option is not supported in API versions greater than 4.0.
Allow scripts to access the OAuth token is unchecked on the Agent job configuration under phases and on the Build/Options tab (slider set to disabled)
I've googled and searched for all sorts of stuff to try and find someone with the same problem but it's almost like I'm the first to discover this - which is highly unlikely!! It has almost driven me to using Bing to search for a solution, but let's not get carried away.
Any ideas or suggestions would be greatly appreciated!
So it turns out that turning off the "New YAML pipeline creation experience" and "New Navigation" under preview features fixes the problem, insofar as I can now create and save a build pipeline without the error.
Also, if you have "Build YAML Pipelines" enabled under preview features for the Organisation, you get the "View YAML" link that I was missing also.
Thanks all for your help. I'd be interested to know the root cause of this still. I'll update the Microsoft support ticket with the same and post back here if they have any insights.
There's an similar issue here:https://developercommunity.visualstudio.com/content/problem/123012/getting-multiconfiguration-build-option-not-suppor.html
Seems the build template was broken. So, you can try with other build templates or starting over with an empty template, then add the needed tasks manually to check if that works.
Besides, you can try below things:
Clean the caches on your client machine, also clean the browser
caches, then check it again. See How to clear the TFS cache on
client machines.
Create a new team project and create a new build pipeline within the
new team project to check if that works
I am assuming this is a bug in the VSTS system and it will likely be fixed soon. But for the time being, I found a workaround:
I was also getting the AllowScriptsAuthAccess error and struggled with it for hours. I don't think any of the configuration settings you mentioned have anything to do with it (free account, GitHub, OAuth token unchecked).
To solve it, I converted the Agent Job to YAML (which is as easy as clicking "View YAML" in the upper right). Save the code to a file named .vsts-ci.yml, and save this in the root folder of your solution. Commit/push the new file, then queue the build. (Note that the conversion to YAML is one-way, so you may want to Clone your build.)
That should get rid of the AllowScriptsAuthAccess error. After that I had to add a few variables, but then it's just a matter of following the error messages.
I hope this helps. Sorry I can't answer this more authoritatively. Please post a comment if I am missing any steps.
I had this issue and it turned out that I didn't have Build Admin permissions in VSTS for the project. Not a very helpful error message for this.
I've been able to edit and continue for more than a year. I don't know what unfortunate mistake I've made but I'm now not able of editing the code and continuing anymore, as when I try I get the "Changes are not allowed in the following cases".
I've been googling and changing settings for more than half a day straight now! x86, enable and disable, repair VS, 2015 and 2017 versions, check the project settings... As far as I can tell I've touched every single switch I can think of and I still can't edit and continue!
I've noticed though that I can edit and continue on a simple console program (Console.Write and .Read sort of thing) but not on a simple MVC project (the one that comes with the MVC scaffolding) so I'm now thinking is something to do with MVC.
Any thoughts? It's happening even with projects that I could edit and continue with in the past!
Following Karthik recommendation and https://stackoverflow.com/a/27672935/3397630 I just had to remove COR_ENABLE_PROFILING from the system and user variables!
There are a few more similar entries like COR_PROFILER, CORECLR_ENABLE_PROFILING and CORECLR_PROFILER but I left those there.
I've used TFS Power Tools on a daily basis for several months. I particularly depend on Windows Shell Extension.
For about a week now, two issues have come up:
Issue 1
Every time I enter a directory under TFS control, I have to right-click twice to see the TFS context menu
Issue 2
My pretty TFS Green indicators on files/folders are gone:
I've downloaded and reinstalled the Power Tools, but I still have these two issues.
Any thoughts on how to fix this?
**UPDATE**
Dave gave me the answer via link. Just in case that link goes bad, here is the answer:
Open the registry
Go to : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer \ShellIconOverlayIdentifiers
Prefix any "Tfs" folder with numbers (“1TfsOverlayAdd” , “2TfsOverlayEdit” etc.). This allows them to take priority over other icon overlays.
Restart the machine or kill explorer.exe and restart it
As far as the delay issue is concerned, I'm not experiencing that this morning; which is odd. I question that the solution for the overlay was also the solution for the right-clicking.
Everything's back to normal now so I am good to go.
The missing green icons can be explained here. It is because Windows has a limit of overlay icons it supports. The details on how to fix it are in that blog post.
How long are you waiting after entering a folder before you perform the first Right Click? It sometimes takes a while for the TfsComProviderSvr.exe to check if the local folder is a workspace and register the shell extension.
I have an Ab-Initio plan consisting of more than one graphs in it. If the plan failed in one particular graph during its 6th phase, then how can the plan be restarted from the particular graph and that too from the beginning.
Note: Not for the last check point available in the .rec file.
In this case what should i do?
Delete the respective *.rec file from the run directory for the plan it was created. And rerun the graph. As it will not find any recovery file it will execute from the beginning.
One approach would be that you can disable the remaining graphs by selecting them, right click and then select disable. Now when you run your plan, only the enabled process will run without having to rerun the entire process, hope this helps and in case it does, pleas check the tick mark on the left and mark it as a correct answer and upvote.
Abinitio provde excellent first-line support services for their customers. I would recommend you email them support#abinitio.com. From experience it helps if you state your co>op version and your gde version and package the graph in question and send that as well.
I'm using the Build Explorer to delete our project's builds. It's taking forever because it's 'timing out' trying to delete the label and drop location (now that the drop location doesn't exist any more).
So, I'm hoping to do this via the command line to see if I get more love.
Is this possible?
Yes it is, see the following HowTo on MSDN.
How to: Delete a Completed Build (Command-Line)
However, I'm not sure that this is going to improve the situation for you as it basically does the same server calls that the UI does. Give it a try anyway. In the meantime I'll go ask a few folks and I'll edit this answer if we come up with anything to help you with your timeout issues.
The TFS Build Manager utility will let you multi-select and delete. It still works serially but at least it's only one manual step.