How Can i add a task without mention any project and want to set reminder for that in openerp 7.0 ?
I tried it but not getting enough response.
Please help me to dig out this problem.
Let me know if there is anything else i may help you with.
Thanks
I think its working in 7.0. I just created a task without describing project.
without project you want to add task is worthless.
But you can create task without describing project see if you are providing service than you don't need to create project every time for every customer so you can create task directly through task menu as #Ronak Shows
and you can manage it as well as
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 have been working with Pex(IntelliTests) for some time now and I wondered if it is possible to create the tests via some sort of command(or .exe) and not through the IDE(VS2015) with right-clicking the function.
I have an automated process which builds my projects and further runs my tests. However if the IntelliTests are not generated anew for the new implementation they are rather useless.
This may seem like a basic question but unfortunately I could not find any information on the internet.
A command line for IntelliTest is not yet supported. If you would like to see it supported, kindly add your vote here: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/8623015-enable-intellitest-to-run-in-the-build-pipeline
Is anyone aware of a way to define a set of default issues, which can then be attached to a project type definition so that each time a project of this type is created, it comes with these issues?
All of our projects have issues like 'create wireframes','set up local environment' etc. and I'm looking for a quick way to automate this part of project setup.
I have full admin access and I can't see anything in the issue or project setup that does this.
Can't you just create a set of issues in an empty project and export them?
You can use that set and import it into your new project to start with.
Using the ASANA API, I can't find a way to create an unassigned task attached to a project. Ex: I would like to create a task "Add this feature" to workspace "12345678" and add it to project "456789" without assignee.
Any help?
Thanks!
(I work at Asana)
Every project belongs to exactly one workspace, and all tasks in that project must also be in that workspace. Therefore, specifying both project and workspace would be redundant.
That said, if you look at the Task documentation you will see you can specify a projects array at creation time to indicate which projects the new task should be created in.
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.