I have a Wufoo form that, when submitted, creates a new Asana task.
Is there a way to make a "date" field in a Wufoo form automatically set the Due Date in an Asana task? My guess is that there would be a CSS layout keyword for it, but perhaps it doesn't exist.
Any ideas?
(I work at Asana)
We haven't added this functionality yet but hope to in the near future - it is one of our top requests for the Wufoo integration. I'll make a note to update this task when we add it.
Related
I'd like to perform operations like automatically update a field based on another field's value (for example if the assignee field is empty automatically assign to a default, set an hidden "due date" field based on the release-fix start date, ecc.) or write a custom validator that does validations based on a combination of values.
Every time I go searching on the jira forum I find java fragments of code, so everything seems to be possible, but it seems it is only at one condition: to buy the script runner plugin!
It seems strange to me: of course this plugin seems to be doing a lot of boilerplate for you but...what if I want to make a little more effort but still not payng for something that, in my opinion, should be free? I'm already paying the software license...isn't there another way to perform such post actions?
Try MyGroovy. It provides similar features. For tasks like execution post-functions I suppose it would fits good.
In my tests... the newly created tag is not in the get request for tags when it isn't associated with a task. Once associated with a task it seems to appear in the response. However, once removed from a task it disappears from response.
For all intents and purposes, a tag that's no longer associated with any tasks doesn't exist. You may still see autocomplete suggestions due to caching in the web client, but the API won't show them anymore.
The long-term goal is to have tags simply behave like text labels. A string would uniquely identify a tag, and we can stop messing around with IDs and pretending they're proper resources.
I was wondering if there is a way to update a custom field during a workflow transition in JIRA.
The "Update Issue Field" post function is the closest feature I found, but its document explicitly states "This post function cannot update custom fields and must be positioned after the other optional post functions."
I was wondering if there is another function can support my purpose.
JIRA Suite Utilities is the standard add-on everyone uses to do this
https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Post-Functions#JIRASuiteUtilitiesWorkflowPost-Functions-UpdateIssueCustomFieldPost-Function
Not available for OnDemand
EDIT: JIRA Suite Utilities is now available for JIRA Cloud and comes pre-installed in new Cloud instances.
EDIT: And now it is no longer free.
There is a Post Function Update Issue Custom Field now in JIRA OnDemand 7.1. It seems to be pretty limited, e.g. you can't write an expression such as setting the value if it's currently empty.
I'd provide a link to their documentation page but their search claims it doesn't exist.
There is possible to execute Groovy script as Post Function and it let you do almost everything.
For example, here is script, how to update custom field (option) dependent on value of another custom field value.
EDIT: This solution is abel only for hosted instace. Not for Cloud
I'm customizing the Work Item Definition Schema for the 'task' work item in TFS Server 2012. I've created a new field for hold a CustomerReference value. It works as I expected, but I would like add a UNIQUE restriction for security. I'd like add a rule than it makes imposible create two workItems with sme CustomerReference.
I think that none of the rules defined here http://msdn.microsoft.com/en-us/library/cc339553(v=vs.90).aspx achieve my target.
Any idea? Thanks in advance,
As a last resort there is a way to write a custom plug-in that can enforce this server-side. See this link for more info on creating an ISubscriber plug-in: http://nakedalm.com/team-foundation-server-2010-event-handling-with-subscribers/
Unfortunately, the plug-in model doesn't allow you to prevent changes; but it could allow you to detect when somebody has violated the rule and react. For example, it could send an email off to somebody, and possibly clear out the CustomerReference field from the duplicate.
When I use
https://app.asana.com/api/1.0/workspaces/workspace-id/tasks -d "name=this is a new task"
and then also using the POST method... I get a response, but nothing is created in asana...
This is the response in JSON format
{"data":{"id":5480677401703,"created_at":"2013-05-17T12:55:21.298Z","modified_at":"2013-05-17T12:55:21.298Z","name":"","notes":"","completed":false,"assignee_status":"later","completed_at":null,"due_on":null,"workspace":{"id":1337166104874,"name":"mecad.co.za"},"assignee":null,"parent":null,"followers":[{"id":1337166104857,"name":"Andries Koorzen"}],"projects":[],"tags":[]}}
But I don't see anything in asana
I guess you may have problem with the server itself. You would better start the ISS.
Rather, you can control the postLinkClicked method to see if there is a problem.
(I work at Asana) Where do you expect the task to show up? You have not given your new task an assignee or a project, so it will not show up in your My Tasks list, nor will it show up under any project. Try setting something in the assignee or project field.
But it also looks like you have a problem specifying details for the task, since you're attempting to pass a name but it's not being accepted by the system. My guess is something about the way you're doing this is not actually sending the correct POST data to the Asana API.