I wonder if it is possible to perform a task when it becomes available to a user without the user having to click the "take" button. Because I have a process with many tasks and ends up being annoying to have to every time have to click on "take". If it can be done, it would be great if you could give me an example.
If only one user can perform a task you can configure the single actor "actor filter" on the task (or on the lane). By doing so the task will be automatically assigner to the single user that can perform the task.
When using "actor" a user need to "take" the task in order to avoid concurrent actions from several different users that can actually do the task (candidates).
Related
Suppose i have some set of tasks say:-
Analysing Code.
Coding.
Exception Handling.
View Integration
Deployment.
Bug Fixing.
How do i bulk create the same set of tasks under multiple user stories as its respective child objects?
Eg:- say i have
45678,45679,45670,45671,45672 as my user stories.
If i manually create the 6 listed tasks to the 1st user story, then how can i bulk create the same set of tasks to all other user stories as child objects?
There is no automation out of the box for this.
You can use excel to copy/paste the tasks as children of PBI's. There are also some third party tools out there that can do what you want. I built the TFS Event Handler in 2008 for an organization but have not had much call for it since.
http://nakedalm.com/tfs-event-handler-for-team-foundation-server-2010/
The reason I don't get much call for this sort of thing is that if you need it, then you are doing something wrong. Your list above is something that would make a lot more sense on a definition of done than a task list. If this was the DOD then the tasks should be the development teams plan to get them done...
When we launch/initiate a process from process portal in IBM BPM, first human task of the process appears in the work (task inbox). But that user has to claim it explicitly to work on the task and that is a problem in my case.
What I want to achieve is: who ever launches the process from portal should land immediately to first human task so the user doesn't have to claim it explicitly
Unfortunately, this feature is unintuitive and poorly documented. Fortunately, it is very easy to do. It's one of those things that everyone "just knows" and is, by far, everyone's first question when using the product. Here's the trick:
If you set the user distribution for the first human activity in a BPD as "last user" ("last user in lane" for older versions of the product), it has a special meaning to the system that indicates that the task should be immediately assigned the user that started the process and the first coach be immediately displayed (assuming the user has the permissions to that activity, and the BPD is able to immediately flow to that activity).
In theory, this is documented here: http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/index.jsp?topic=%2Fcom.ibm.wbpm.main.doc%2Fic-homepage-bpm.html under "last user", but the docs are very confusing. Even to me, and I know what it is supposed to be saying.
If you want to make the user to flow human tasks without return to his/her inbox in
process portal
so you should do from process designer two things
first put the assignment to be last user in the lane
and the second make true on check box on every task in the land you
want to follow automatically to next task.
I am working on an application that needs to take some actions when certain events happen in user's Asana account (such as new task created, new project created and existing task modified). For this I plan to poll the Asana API every 15 mins and check for new activities. At the moment, for new task created event, I am polling the project for all its tasks in one go, but I do not get any time stamp in return. For timestamps I am required to make individual API calls for each task, which will be inefficient and eat into my rate quota.
Could you please let me know what is the best way for me to get information on new task or project created in Asana for a user, without impacting the rate quota a lot?
You can include timestamps and other data using the opt_fields parameter. So for instance, if you just want to know about newly-created tasks, you can use GET .../tasks?opt_fields=created_at,name (assuming you want the name as well).
Hope that helps! (Also, we're working on a subscription system that lets you "listen" to events like task creation, which will be even better - but that's still in the works.)
I have a Rails website with three tables: User, Task, and TaskInstance. The Task table is like a master list of tasks, not coupled to any particular user, whereas the TaskInstance table contains records that indicate a user's completion of a particular task. In other words, a TaskInstance has a User id, a Task id, and a completion status (boolean). A User has many TaskInstances.
I'd like to allow administrators to add new Tasks. Doing so should create a new TaskInstance for that Task for every User. However, that doesn't sound like it would scale well. Say I have fifty thousand Users, creation of a new Task would require fifty thousand TaskInstances to be created immediately on the spot.
It would be good if some sort of lazy loading could be done instead, but I don't know where I would do it. I could do it at login e.g. when a User logs in, check if a new Task has been created; if so, create a new TaskInstance only for that particular User. But then what about users that are already logged in when the new Task is created?
I guess I'm just wondering what the preferred approach to this sort of problem is.
Move this to the community wiki if you need to.
Don't create the TaskInstances right upfront, but only when they are needed. Since a new Task gets created anyway, it can be displayed to any User, no matter if there is a TaskInstance or not. As soon as a user decides to start with a Task, the TaskInstance should get instantiated.
Our team is getting started with using user stories for gathering requirements. We are experiencing some confusion about how they should be mapped to tasks. It seems we have several user stories that describes different aspects of the same fundamental development task. For example...
User stories:
As an XYZ user, I want to enter targets into a form, so that I can track progress towards them
As an XYZ user, I want to only be able to enter positive integers for a target, so that I can't enter erroneous data
As an XYZ user, I want to filter on available targets, so that I can focus only on particular ones
Task:
Develop a form for entering targets with validation and filtering
The problem here is that we are using TFS which prevents a development task from having multiple parents. Presumably this is because we are getting this approach wrong somehow in the first place.
Can anyone please suggest how this should be done?
We have exactly the same challenge in our projects. And it OK to have a task that provides (part of) the required functionality embedded in the user stories.
How we handle this:
Relate the task as a CHILD to the user story with the highest priority after release/sprint planning is done.
Relate the same task as RELATES TO to the other user stories.
In practice, the task hours are rolled-up into the first user story being processed. The task is then already done when the following user stories are put into sprints.
Would that work for you?
Firstly in the example above the task has three components at least
form
validation
filtering
it looks like three tasks three stories
solved?