US20230251880A1 - Systems and methods to facilitate task-specific workspaces for a collaboration work management platform - Google Patents
Systems and methods to facilitate task-specific workspaces for a collaboration work management platform Download PDFInfo
- Publication number
- US20230251880A1 US20230251880A1 US18/305,100 US202318305100A US2023251880A1 US 20230251880 A1 US20230251880 A1 US 20230251880A1 US 202318305100 A US202318305100 A US 202318305100A US 2023251880 A1 US2023251880 A1 US 2023251880A1
- Authority
- US
- United States
- Prior art keywords
- task
- user
- workspace
- applications
- specific
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 230000003993 interaction Effects 0.000 claims abstract description 62
- 230000009471 action Effects 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 7
- 230000001419 dependent effect Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 11
- 230000005540 biological transmission Effects 0.000 description 6
- 230000000977 initiatory effect Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 4
- 238000004590 computer program Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000007613 environmental effect Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063114—Status monitoring or status determination for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G5/00—Control arrangements or circuits for visual indicators common to cathode-ray tube indicators and other visual indicators
- G09G5/14—Display of multiple viewports
Definitions
- the disclosure relates to systems and methods to facilitate task-specific workspaces for a collaboration work management platform.
- Generic computer interfaces offer few if any options for limiting distractions. Employees often lose time, efficiency, and/or focus because of interruptions, distractions, switching between tasks and losing their place/train of thought, etc.
- Existing interfaces fail to offer clean workspaces that enable a user to transition between tasks efficiently, without losing their work and/or place.
- Existing management platforms and/or interfaces often offer too many choices and/or options that make it difficult to actually get work done because users are overwhelmed and/or distracted by the interface.
- the disclosure relates to systems and methods configured to facilitate task-specific workspaces for a collaboration work management platform.
- the task-specific workspaces may provide a focused workspace in which users can work with fewer distractions.
- the applications and/or windows open within the task-specific workspace may be related to and/or used for working on a specific task such that users are not distracted by windows and/or applications that are unrelated to the task they are currently working on.
- the state of the task-specific workspace and/or the user’s interactions with the windows and/or applications within the task-specific workspace may be saved. As such, the user may be able to return to where they left off within the task-specific workspace at a later time.
- the state of the word document, the internet browser, and/or the presentation application may be saved such that when the user re-starts and/or re-selects the task, the applications and/or windows corresponding to the word document, the internet browser, and/or the presentation application automatically open.
- the applications and/or windows corresponding to the word document, internet browser, and/or presentation application may automatically open in the same arrangement and/or to the same section of the word document, internet webpage, and/or slide the user was working on at or near the time they paused the task and/or switched tasks.
- the task-specific workspaces may takeover a desktop of a user.
- the user may be presented with one or more tasks (e.g., a task list, etc.) rather than all of the different applications and/or documents that are typically presented with existing desktops. This may clutter the desktop, overwhelm the user, and/or distract the user from the tasks they need to complete.
- Users often work from various different devices (e.g., multiple computers, mobile devices, etc.) having to save things locally and/or transfer them from one device to another.
- Task-specific workspaces automatically track and maintain the state of the workspace such they the user could pick up where they previously left off on the same device and/or across different devices. This reduces the need to save things locally on devices, eliminates extra steps of uploading saved documents to a file-share program and/or emailing saved documents, and solves the problems associated with lost time getting users up to speed and/or picking up where they left off.
- the presentation of the collaboration environment may be based on environment state information.
- the storage component may be configured to effectuate storage of the environmental state information.
- the environmental state information may define the state of the collaboration environment.
- the state of the collaboration environment may comprise a user state, a project state, a task state, and/or or other states that make up the collaboration environment state.
- the environmental state information may include one or more records.
- the one or more records may include one or more user records, project records, task records, and/or other records.
- the user state may be defined by one or more of the user records.
- the user records may define values of user parameters associated with users interacting with, viewing, and/or able to interact with or view the collaboration environment.
- the project state may be defined by the project records.
- the project records may define values of project parameters for projects managed within the collaboration environment.
- the task state may be defined by the task record.
- the task record may define values of task parameters for tasks created and/or assigned within the collaboration environment.
- a system configured to facilitate task-specific workspaces for a collaboration work management platform may include one or more of: one or more servers, one or more client computing platforms, and/or other components.
- the one or more servers may be configured to communicate with one or more client computing platforms according to a client/server architecture and/or other architecture.
- the one or more servers and/or client computing platforms may include one or more physical processors configured to execute one or more computer program components.
- the computer program components may include one or more of an environment state component, a collaboration environment component, a user task component, a desktop component, a workspace component, an application component, and/or other components.
- the one or more client computing platform(s) may be configured to facilitate task-specific workspaces for individual ones of the users for individual tasks.
- the one or more tasks may include action items, to-do items, and/or objectives within a given project managed via the collaboration work management platform.
- the one or more tasks may be assigned to one or more users such that the one or more tasks assigned to a given user may appear on a given user’s task list within the collaboration environment.
- User task component may be configured to receive user input indicating selection of a first task. User task component may be configured to effectuate presentation of the first task for the first user. Presentation of the first task for the first user may be based on the environment state information. Responsive to the first user selecting the first task, the user task component may be configured to request information associated with the first task (e.g., a first user record, a first project record, a first task record, and/or other information) from the server. The server may effectuate transmission of the first user record, the first project record, the first task record, and/or other records over the network to the user task component.
- information associated with the first task e.g., a first user record, a first project record, a first task record, and/or other information
- desktop component may be configured to clear the current desktop of a given client computing platform.
- the desktop may be cleared to initiate a clean workspace (e.g., a first task-specific workspace) for the first task.
- a clean workspace e.g., a first task-specific workspace
- the workspace component may be configured to effectuate presentation of the first task-specific workspace for the first task.
- a first set of applications may be accessible by the first user via the first task-specific workspace.
- the first set of applications may have one or more corresponding windows through which the first user interacts with the first set of applications.
- the first user may work on the first task using one or more applications in the first set of applications.
- the workspace component may be configured to block and/or restrict one or more applications within the task-specific workspace. As such, one or more other applications generally available via the first client computing platform outside of the task-specific workspace, may not accessible within the first task-specific workspace.
- the workspace component may be configured to receive user input indicating a pause and/or completion of the first task at a first time.
- a pause of the first task may be indicated by switching to a second task and/or another task.
- the application component may be configured to obtain information characterizing interactions of the users with the applications within the task-specific workspaces at or near the time the task is paused.
- the application component may be configured to obtain information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near the first time.
- the interactions may include, for example, information indicating which applications the user had open, which webpage(s) and/or file(s) the user had open, the application and/or document titles the user was working on and/or had open, progress information characterizing progress of the first user within the first set of applications (e.g., where the user left off in one or more webpages and/or files), and/or on the first task (e.g., the user paused the task when 60% completed), an amount of time spent on active applications and/or webpages, and/or other interactions.
- the application component may be configured to store the information characterizing the interactions of the first user with the first set of applications at or near the first time.
- the information characterizing the interactions of the first user with the first set of applications at or near the first time may be stored as part of a first user record and/or a first task record.
- the workspace component may be configured to minimize and/or close the one or more windows corresponding to the first set of applications for the first task responsive to the receiving the user input indicating the first task is paused and/or completed.
- the workspace component may be configured to restore the first set of applications based on the environment state information.
- the first set of applications and/or the one or more windows corresponding to the first set of applications may be restored (e.g., re-opened, re-arranged, reverted, etc.) based on the first user record and/or the first task record.
- FIG. 1 illustrates a system configured to facilitate task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations.
- FIG. 2 A illustrates an exemplary graphical user interface for initiating a task-specific workspace, in accordance with one or more implementations.
- FIG. 2 B illustrates an exemplary application recommendation interface for a task-specific workspace, in accordance with one or more implementations.
- FIG. 2 C illustrates an exemplary task-specific workspace, in accordance with one or more implementations.
- FIG. 2 D illustrates an exemplary graphical user interface for pausing a task-specific workspace, in accordance with one or more implementations.
- FIG. 3 illustrates a method to facilitate task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations.
- FIG. 1 illustrates a system 100 configured to facilitate task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations.
- system 100 may be configured to effectuate presentation of a collaboration environment based on environment state information. Users may view and/or interact with the collaboration environment. One or more projects may be managed within the collaboration environment. One more tasks may be created and/or assigned to one or more users within the collaboration environment.
- the presentation of the collaboration environment may be based on environment state information.
- the environment state information may include user records 128 , project records 130 , task records 132 , and/or other records.
- the environment state information may be continuously generated and/or updated based on the state of the collaboration environment representing the users’ interactions with the collaboration environment.
- the state of the collaboration environment may include a user state, a project state, a task state, and/or other states.
- the user state may be defined by user records 128 .
- User records 128 may define values of user parameters associated with users interacting with and/or viewing the collaboration environment.
- the project state may be defined by project records 130 .
- Project records 130 may define values of project parameters for projects managed within the collaboration environment.
- the task state may be defined by task records 132 .
- Task records 132 may define values of task parameters for tasks created and/or assigned within the collaboration environment.
- the user parameters associated with the users interacting with and/or viewing the collaboration environment may include parameters describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information.
- Individual ones of the users may be associated with individual ones of the user records.
- a user record may define values of the user parameters associated with a given user interacting with and/or viewing the collaboration environment.
- the user parameters may, by way of non-limiting example, include one or more of: a user name, a user role, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more projects (which may include project parameters defined by one or more project records); one or more tasks (which may include one or more task parameters defined by one or more task records), one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, etc.), one or more authorized applications, one or more presence/interaction parameters (e.g., indicating presence and/or interaction level at an environment level, project level, task all, application level, etc.), one or more notification settings, one or more progress parameters, status information for one or more tasks the user is associated with, one or more statistics related to a given user (e.g., how many tasks the user has completed, how quickly the user completed the tasks, the efficiency of the user, bandwidth of
- the project parameters for projects managed within the collaboration environment may include parameters describing one or more projects managed within the collaboration environment and/or via the collaboration work management platform, and/or the metadata associated with the one or more projects. Individual ones of the projects may be associated with individual ones of the project records.
- a project record may define values of the project parameters associated with a given project managed within the collaboration environment and/or via the collaboration work management platform.
- a given project may have one or more owners and/or one or more team members working on the given project.
- the given project may include one or more tasks assigned to one or more users under the given project heading.
- the project parameters may, by way of non-limiting example, include one or more of: one or more tasks within individual ones of the projects (which may include task parameters defined by one or more task records), one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), a project name, a project description, one or more project dates (e.g., a start date, a due date, a completion date, and/or other project dates), one or more project members (e.g., an owner, one or more other project members, member access information, and/or other project members and/or member information), a status and/or progress (e.g., an update, a hardcoded status update, a measured status, quantity of tasks remaining in a given project, completed tasks in a given project, and/or other status parameter), one or more attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g
- the task parameters for tasks within the collaboration environment may include parameters describing one or more tasks created and/or assigned within the collaboration environment and/or via the collaboration work management platform, and/or the metadata associated with the one or more tasks. Individual ones of the tasks may be associated with individual ones of the tasks records.
- a task record may define values of the task parameters associated with a given task created and/or assigned within the collaboration environment and or via the collaboration work management platform.
- the tasks make include one or more to-do items, action items, objectives, and/or other tasks one or more users should and/or plan on accomplishing. Tasks may be created by a given user for the given user and/or created by the given user and assigned to one or more other users.
- the task parameters may, by way of non-limiting example, include one or more of: a task name, a task a description, a task status (e.g., complete, incomplete, and/or another status), an assignee, one or more followers, one or more team members, one or more task dates (e.g., a start date, a completion date, a due date, and/or other dates), one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), task upvotes, other hard-coded task responses, one or more tags, one or more custom fields (e.g., priority, cost, stages, and/or other custom fields), one or more dependencies (e.g., tasks dependent on, dependent tasks.
- a task name e.g., complete, incomplete, and/or another status
- a task dates e.g., a start date, a completion date
- a task URL Users assigned to dependent tasks, notification settings for dependent tasks, and/or other dependencies
- a task URL one or more subtasks and/or subtask parameters (e.g., name, description, hardcoded status, assignees, due date, state date, comments, upvotes, tags, and/or other subtask parameters), one or more attachments, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), state of a workspace for a given task (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a given task), other task parameters for the given task, and/or other task parameters, user parameters, and/or project parameters for one or more users and/or project(s) the given task is associated with.
- interaction parameters e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters
- any metadata and/or values of parameters related to any users, projects, and/or tasks may be considered values of user parameters, project parameters, and/or task parameters.
- user parameters may be used interchangeably herein.
- system 100 may include one or more of: one or more servers 102 , one or more client computing platforms 124 , external resources 122 , and/or other components. Users may interact with system 100 via one or more client computing platforms 124 .
- the one or more servers 102 may be configured to communicate with one or more client computing platforms 124 according to a client/server architecture and/or other communication schemes.
- the one or more client computing platforms 124 may include one or more of a cellular telephone, a smartphone, a digital camera, a laptop, a tablet computer, a desktop computer, a television set-top box, smart TV, a gaming console, and/or other client computing platforms.
- the one or more servers 102 may include one or more physical processors 104 and/or physical processors 105 (also referred to herein as “one or more processors” and/or “processor(s)”), non-transitory electronic storage 126 , and/or other components.
- Non-transitory electronic storage 126 may include one or more records.
- the one or more records may store the environment state information that defines the state of the collaboration environment.
- the state of the collaboration environment may include a user state, a project state, a task state, and/or other states.
- the records may include user records 128 , project records 130 , task records 132 , and/or other records.
- the one or more physical processors 104 may be configured to access one or more of user records 128 , project records 130 , task records 132 , and/or other records to effectuate transmission of the environment state information over network 132 to client computing platform(s) 124 .
- Client computing platform(s) 124 may use the environment state information to effectuate presentation of the collaboration environment via client computing platform(s) 124 .
- the one or more physical processors 104 and/or physical processors 105 may be configured to execute machine-readable instructions 106 and/or machine-readable instructions 107 .
- the machine-readable instructions 106 may include one or more computer program components.
- the computer program components may include one or more of an environment state component 108 , a collaboration environment component 110 , a user task component 112 , a desktop component 114 , a workspace component 116 , an application component 118 , a and/or other components.
- server(s) 102 may be configured to provide remote hosting of the features and/or functions of machine-readable instructions 106 to one or more client computing platform(s) 124 that may be remotely located from server(s) 102 .
- one or more features and/or functions of server(s) 102 may be attributed as local features and/or functions of one or more client computing platform(s) 124 .
- individual ones of the client computing platform(s) 124 may include one or more additional machine-readable instructions 107 comprising the same or similar components as machine-readable instructions 106 of server(s) 102 .
- the client computing platform(s) 124 may be configured to locally execute the one or more components that may be the same or similar to the machine-readable instructions 106 .
- One or more features and/or functions of machine-readable instructions 106 of server(s) 102 may be provided, at least in part, as an application program that may be executed at a given client computing platform 124 .
- One or more features and/or functions of machine-readable instructions 107 may be provided, at least in part, at a server(s) 102 .
- the electronic storage 126 may include electronic storage media that electronically stores information.
- the electronic storage media of electronic storage 126 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with one or more servers 102 and/or removable storage that is removably connected to one or more servers 102 .
- the connection may be facilitated by, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.).
- the electronic storage 126 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media.
- the electronic storage 126 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources).
- the electronic storage 126 may store software algorithms, information determined by processor(s) 104 , information received by one or more servers 102 , information received by client computing platforms 124 , and/or other information that enables one or more servers 102 to function as described herein.
- the electronic storage 126 may be configured to store one or more records and/or information.
- the one or more records may include one or more of user records 128 , project records 130 , task records 132 , and/or other records.
- the one or more records may specify and or define values for one or more user parameters, project parameters, and/or other parameters for the collaboration environment.
- the one or more records may specify correspondences between one or more of the user records 128 , project records 130 , task records 132 , and/or other records. The correspondences may be used to determine which user parameters and/or values, project parameters and/or values, and/or task parameters and/or values are associated with a given user, project, and/or task within the collaboration environment.
- the client computing platform(s) 124 may monitor, and/or collect information for transmission to the one or more server(s) 102 to be stored as environment state information.
- the client computing platform(s) 124 may obtain and/or collect environment state information from the one or more server(s) 102 .
- the environment state component 108 of machine-readable instructions 106 may be configured to effectuate transmission of the environment state information to client computing platform(s) 124 , and/or vice versa.
- environment state component 108 may be configured to receive information over network 132 from client computing platforms(s) 124 .
- Environment state component 108 may be configured to effectuate storage of the received information as environment state information to one or more user records 128 , project records 130 , task records 132 , and/or other records.
- Environment state component 108 may be configured to obtain one or more user records 128 , project records 130 , task records 132 , and/or other records in response to and/or based on one or more requests from client computing platform(s) 124 .
- Environment state component 108 may be configured to effectuate transmission of values for user parameters, values for project parameters, values for task parameters, and/or other state information to client computing platform(s) 124 .
- the values for user parameters, values for project parameters, values for task parameters, and/or other state information may be used to effectuate presentation of the relevant tasks and/or projects for a given user of the collaboration environment associated with the given client computing platform 124 to which the values and/or other state information is transmitted.
- Collaboration environment component 110 of machine-readable instructions 107 may be configured to effectuate presentation of a collaboration environment. Presentation of the collaboration environment may be based on environment state information.
- the environment state information may include user records, project records, task records, and/or other records.
- the environment state information may define a state of the collaboration environment.
- the state of the collaboration environment may include a user state, a project state, a task state, and/or other states.
- the user state may be defined by the user records.
- the user records may define values of user parameters associated with users interacting with and/or viewing the collaboration environment.
- the project state may be defined by the project records.
- the project records may define values of project parameters for projects managed within the collaboration environment.
- the task state may be defined by the task records.
- the task records may define values of task parameters for tasks created and/or assigned within the collaboration environment.
- the client computing platform(s) 124 may effectuate presentation of the collaboration environment.
- the collaboration environment may include the environment in which users interact with and/or view the one or more tasks and/or projects managed via the collaboration work management platform.
- the collaboration environment may exist whether or not a given user is viewing and/or interacting with the collaboration environment.
- projects managed vie the collaboration environment may include one or more tasks.
- the one or more tasks may include action items, to-do items, and/or objectives within a given project.
- the one or more tasks may be assigned to one or more users such that the one or more tasks assigned to a given user may appear on a given user’s task list within the collaboration environment.
- the one or more client computing platform(s) 124 may be configured to facilitate task-specific workspaces for individual ones of the users for individual ones of the tasks.
- User task component 112 may be configured to receive user input indicating selection of a task.
- the user input may indicate selection of a first task.
- User input may include any input and/or indication by a user to start and/or work on the first task.
- user task component 112 may effectuate presentation of multiple tasks associated with the first user (e.g., assigned to the first user).
- User task component 112 may be configured to obtain user input indicating a selection of the first task from the multiple tasks.
- user task component 112 may be configured to determine a recommended task (e.g., which task a user should work on) based on the environment state information.
- the recommended task may be determined, for example, based on the due date, one or more dependencies of the recommended tasks, efficiency and/or time information associated with the given user and/or task (e.g., it is 3 pm and task one is predicted to take the user 2 hours to complete while task two is predicted to take the user 4 hours to complete, the first task may be recommended if, for example, the user typically becomes inactive in the collaboration environment after 5:00 p.m.), one or more other tasks associated with the given user (e.g., the user has 4 other tasks due tomorrow), and/or other information.
- a recommended task e.g., which task a user should work on
- the recommended task may be determined, for example, based on the due date, one or more dependencies of the recommended tasks, efficiency and/or time information associated with the given user and/or task (e.g., it is 3 pm
- user task component 112 may be configured to determine and/or effectuate presentation of one or more recommended applications, documents, updates, and/or other information for working on the first task.
- the one or more recommended applications, documents, updates, and/or other information may be presented and/or determined responsive to receiving user input indicating selection of the first task.
- the one or more recommended applications may be determined based on user information (e.g., historical user information, user preferences, etc.); task information (e.g., a type of task, the task title, the task due date, etc.); generated work, documents, applications used, and/or other information from one or more dependent tasks, similar tasks, associated tasks, and/or tasks that are otherwise linked to task; one or more updates, interactions, and/or events within a given task, project, and/or task-specific workspace; and/or one or more updates, interactions, and/or events within a given task, project, task-specific workspace that occurred while the given user was not in the task-specific workspace and/or working on the given task, and/or other information.
- user information e.g., historical user information, user preferences, etc.
- task information e.g., a type of task, the task title, the task due date, etc.
- the one or more documents, updates, and/or other information may be determined based on other generated work, documents, applications, and/or other information from one or more dependent tasks, similar tasks, associated tasks, and/or tasks that are otherwise linked.
- user task component 112 may be configured to determine and/or effectuate presentation of one or more recommended applications, documents, updates, and/or other information based on one or more updates, interactions, and/or events within a given task, project, and/or task-specific workspace that occurred while the given user was not in the task-specific workspace and/or working on the given task. As such, the state of a given task-specific workspace may be maintained while a user is not working on the given task and/or within the given task-specific workspace.
- User task component 112 may be configured to effectuate presentation of the first task for the first user based on the environment state information. Responsive to the first user selecting the first task, user task component 112 may be configured to request information associated with the first task from environment state component 108 .
- Information associated with the first task may include user state information associated with the first user (e.g., the first user record), project state information associated with a first project (e.g., the first project record) under which the first task may be assigned to the first user, task state information associated with the first task (e.g., the first task record), and/or other information.
- User task component 112 may be configured to receive the environment state information associated with the first task such that the first task may be presented to the first user.
- desktop component 114 may be configured to clear the current desktop of a given client computing platform 124 .
- Desktop component 114 may be configured to clear the current desktop to initiate the first task-specific workspace for the first task.
- the current desktop may be cleared by minimizing and/or closing one or more open applications and/or windows displayed on the current desktop.
- Desktop component 114 may be configured to clear the current desktop responsive to the current desktop including one or more open applications or windows, and/or responsive to user task component 112 receiving user input receiving user input indicating selection of a first task.
- Workspace component 116 may be configured to effectuate presentation of the first task-specific workspace for the first task.
- the first task specific workspace may include a task header bar including one or more of a task name and/or an indication of the first task that the user is working on within the first task-specific workspace, a project the task is associated with, a due date, a timer button (e.g., for timing how long a user works on a given task), a status button (e.g., for indicating when a task is complete), a chat and/or message button (e.g., for initiating a comment and/or chat session re the first task, and/or other information.
- a timer button e.g., for timing how long a user works on a given task
- a status button e.g., for indicating when a task is complete
- chat and/or message button e.g., for initiating a comment and/or chat session re the first task, and/or other information.
- One or more applications may be available via the task-specific workspace.
- the user may use the one or more applications while working on the given task associated with the task-specific workspace.
- the applications may include: one or more internet applications (e.g., Internet Explorer, Chrome, etc.), one or more document applications (e.g., Microsoft Word, Pages, Adobe Acrobat, Writer, etc.), one or more presentation applications (e.g., PowerPoint, Keynote, etc.), one or more email applications (e.g., Outlook, Gmail, Yahoo mail, etc.), one or more messaging applications (e.g., Slack, Skype, etc.), one or more spreadsheet applications (e.g., Excel, Numbers, etc.), one or more photo/video applications (e.g., photoshop, iPhoto, iMovie, Adobe, Vegas Pro, etc.), and/or other applications (e.g., Genome browser, etc.).
- a first set of applications may be accessible via the first task-specific workspace.
- the first set of applications may be accessible via
- the first set of applications may comprise the available applications within the first task-specific workspace.
- the first set of applications may not include all of the applications accessible via the first-task specific workspace.
- one or more applications in addition to those from the first set of applications may and/or may not be accessible within the first task-specific workspace.
- the first set of applications may include one or more applications the first user interacts with while working on the first task within the first task specific workspace.
- one or more other applications generally available via the first client computing platform outside of the task-specific workspace may not be accessible within the first task-specific workspace.
- Workspace component 116 may be configured to block and/or restrict one or more applications.
- workspace component 116 may be configured to determine one or more other applications that are not accessible within the first task-specific workspace.
- Workspace component 116 may be configured to determine which applications are not accessible based on one or more values for one or more of the user parameters, the project parameters, the task parameters, and/or other parameters indicating the one or more other applications are restricted while the first user is working on the first task via the first task specific workspace.
- the user parameters, project parameters, task parameters, and/or other parameters indicating the one or more other restricted applications may include task settings and/or user settings indicating which applications to restrict and/or make available for the first task-specific workspace.
- a user e.g., the first user, a project and/or task owner, etc. may determine the user settings.
- Workspace component 116 may be configured to receive user input indicating a pause and/or completion of the first task at a first time.
- the user input may be received via a pause button within the task-specific workspace.
- pausing a task may cause the timer to pause.
- User input indicating a pause and/or completion of the first task may include switching from one task to another (e.g., via selecting another task).
- the user input indicating a pause of the first task at the first time may include a selection of a second task.
- Application component 118 may be configured to obtain information characterizing interactions of the users with the applications within the task-specific workspaces at or near the time the task is paused. In some implementations, application component 118 may be configured to obtain information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near the first time.
- Interactions of the first user with the first set of applications within the first task-specific workspace may include, for example, one or more of information indicating which applications the user had open; which webpages, documents, and/or files the user had open; the application and/or document titles the user was working on and/or had open; progress information characterizing progress of the first user within the first set of applications (e.g., where the user left off in one or more webpages and/or files) and/or on the first task (e.g., the user paused the task when 60% completed), an amount of time spent on active applications, documents, and/or webpages; and/or other interactions.
- application component 118 may be configured to monitor interactions of the first user with the first set of applications within the first task-specific workspace. The interactions may be monitored until the first time such that the state of the first set of applications at the first time may be obtained.
- Application component 118 may be configured to store the information characterizing the interactions of the first user with the first set of applications at or near the first time as part of a first user record and/or a first task record. In some implementations, application component 118 may be configured to effectuate transmission of the first user record and/or the first task record over network 132 to environment state component 108 to store as part of one or more user records 128 and/or task records 132 in electronic storage 126 .
- workspace component 116 may be configured to minimize and/or close the one or more windows corresponding to the first set of applications for the first task.
- workspace component 116 may be configured to effectuate presentation of an option to save and/or store the first task-specific workspace and/or the interactions of the first user with the first set of applications within the first task-specific workspace.
- the first-task specific workspace and/or the interactions of the first user with the first set of applications within the first task-specific workspace may be automatically stored responsive to the user pausing the first task, switching tasks, completing the first task and/or otherwise indicating a pause of the first task.
- workspace component 116 may effectuate presentation of an option to save the task-specific workspace responsive to the user indication the status of the task-specific workspace is complete (e.g., the user changing the status from incomplete to complete).
- workspace component 116 may be configured to effectuate presentation of an option to send a notification based on progress of the first user in the first task to one or more interested parties.
- the one or more interested parties may be defined by the environment state information.
- workspace component 116 may be configured to effectuate presentation of an option to send a notification indicating the status and/or progress of the task to one or more followers, team-members, dependent task assignees, project owners, dependent task followers and/or team members, and/or other interested parties.
- Workspace component 116 may be configured to restore one of more applications based on the state information responsive to a user re-opining and/or re-starting a task and/or a task-specific workspace.
- workspace component may be configured to restore the first set of applications based on the environment state information.
- the first set of applications may be restored by workspace component 116 responsive to receiving information indicating re-selection of the first task and/or a re-start of the first task.
- the first set of applications and/or the one or more windows corresponding to the first set of applications may be restored based on the first user record and/or the first task record.
- the first user may be able to pick up working on the first task where he or she left off (e.g., with the correct applications open, on the right page, etc.).
- Re-selecting and/or re-starting a given task may include initiating start of a given task after a user has previously worked on the given task within the given task-specific workspace.
- the same user and/or a different user may re-start and/or re-select the given task.
- a different user may re-select and/or re-start the given task and/or the given task-specific workspace even if the user has not previously worked on the given task within the given workspace.
- a second user may re-select and/or re-start the given task and/or the given task-specific workspace (e.g., even though the second user may and/or may not have previously worked on the given task and/or within the given task-specific workspace).
- the task-specific workspace may be associated with and/or assigned to a given task (instead of an/or in addition to a given user). As such, the task-specific workspace may be transferable such that another user may be able to pick up working on the task where the first user left off. As such, tasks may be reassigned and/or transferred to other users without losing progress on the task.
- Restoring the first set of applications may include un-minimizing and/or opening the one or more windows corresponding to individual ones of the first set of applications the first user was working on at and/or near the first time.
- restoring the first set of applications may include un-minimizing, re-opening, arranging, closing, minimizing but opening to the correct page, and/or otherwise restoring the first set of applications and/or corresponding windows to the state they were in at or near the first time.
- the one application and/or corresponding window may be restored (e.g., un-minimized, re-opened, closed, minimized but open to the correct page, and/or otherwise restored to the state it was in at or near the first time) when the first user returns to the first task-specific workspace.
- restored e.g., un-minimized, re-opened, closed, minimized but open to the correct page, and/or otherwise restored to the state it was in at or near the first time
- the four active applications and/or corresponding window may be restored (e.g., un-minimized, re-opened, open to the correct page, and/or otherwise restored to the state they were in at or near the first time) and the two minimized applications and/or corresponding window may be restored (e.g., minimized but loaded to the correct page/location, and/or otherwise restored to the state they were in at or near the first time) when the first user returns to the first task-specific workspace.
- restoring one or more of the applications in a given set of applications may include identifying one or more corresponding applications that are similar to the applications previously used within the task specific workspace and/or restoring the one or more corresponding applications.
- one or more corresponding applications may be restored based on the first environment state information responsive to a given user re-selecting and/or re-starting the first task via the second computer.
- the one or more corresponding applications may perform the same and/or similar functions as the one or more applications to which they correspond.
- the corresponding application may include google Chrome on the second computer.
- user preferences may be taken into account to determine one or more corresponding applications to recommend to a given user.
- workspace component 116 may determine Chrome should be recommended (e.g., based on the user records, user preferences, etc.) responsive to a given user re-selecting and/or re-starting the first task via the second computer.
- workspace component 116 may be configured to restore one of more applications based on the state information including one or more interactions and/or updates that occurred while that first user was not working on the first task and/or within the first task-specific workspace. Other users may interact with the first task and/or the first task specific workspace while the first user is not. As such, by way of non-limiting example, if a second user worked on the first task after the first user paused the first task, the interactions and/or progress of the second user on the first task and/or within the first task-specific workspace may be captured within the state information such that when restored by the first user, the interactions and/or progress of the second user may be reflected.
- the state of the first task and/or the first task-specific workspace may be updated based on user interactions, updates and/or work product by one or more other users and/or interactions, updates, and/or work product from one or more related tasks (e.g., dependent tasks, etc.), projects, and/or other information.
- related tasks e.g., dependent tasks, etc.
- task-specific workspace may include a group workspace that is updated and/or restored according to the state information reflecting interactions and/or progress of one or more users in the group.
- some interactions, applications, and/or progress may be user-specific such that the task-specific workspace tracks the state of the task-specific workspace as a whole and/or for individual users within the group of users.
- workspace component 116 may be configured to effectuate presentation of a second task-specific workspace.
- User task component 112 may be configured to receive user input indicating selection of the second task.
- the second task may be another task assigned to the first user and/or presented to the first user via the collaboration environment.
- User task component 112 may effectuate presentation of the second task for the first user based on the environment state information.
- Workspace component 116 may be configured to effectuate presentation of a second task-specific workspace for the second task.
- a second set of applications may be accessible via the second task-specific workspace.
- the second set of applications may have one or more corresponding windows through which the first user interacts with the second set of applications.
- One or more applications in the second set of applications may be different than the applications in the first set of applications.
- Workspace component 116 may be configured to receive user input indicating a pause and/or completion of the second task, and/or a re-selection of the first task and/or another task at a second time.
- Application component 118 may be configured to obtain information characterizing interactions of the first user with the second set of applications within the second task-specific workspace at or near the second time.
- Application component 118 may be configured to store the information characterizing the interactions of the first user with the second set of applications at or near the second time as a second user record and/or a second task record, Workspace component 116 may be configured to minimize and/or close the one or more windows corresponding to the second set of applications for the second task.
- Workspace component 116 may be configured to restore the second set of applications based on the environment state information.
- the second set of applications may be restored responsive to responsive to receiving information indicating re-selection of the first task and/or another task, and/or pausing of the second task.
- the one or more windows corresponding to the second set of applications may be restored based on the second user record and/or the second task record.
- FIG. 2 A illustrates an exemplary graphical user interface for initiating a task-specific workspace, in accordance with one or more implementations.
- Desktop 200 may be presented via a client computing platform the same as or similar to one of client computing platform(s) 124 .
- Desktop 200 may include graphical user interface (GUI) 202 .
- GUI 202 may be configured to effectuate presentation of task 210 to which the user is assigned.
- GUI 202 may present a greeting 201 , description of task 210 , due date 212 , assignee 214 , and/or other information associated with task 210 .
- Greeting 210 may welcome the user and/or indicate how much time the user has to work on task 210 .
- task 210 may be a highest priority task indicated by a high priority field 204 based on it having a higher priority than the three other tasks assigned to the user, an earlier due date, one or more dependent tasks, and/or other information.
- GUI 202 may be presented to the user in order to initiate a task-specific workspace. Responsive to the user clicking on button 206 to begin task 210 , a task-specific workspace for task 210 may be initiated.
- FIG. 2 B illustrates an exemplary application recommendation interface for a task-specific workspace, in accordance with one or more implementations.
- application recommendation interface 250 may present one or more recommended applications 252 for task 210 responsive to the user selecting and/or initiating work on task 210 .
- Application recommendation interface 250 may include a “launch all” button 254 that enables the user to launch all of recommended applications 252 .
- one or more of recommended applications 252 may be determined based on user information (e.g., historical user information, user preferences, etc.); task information (e.g., a type of task, the task title, the task due date, etc.); generated work, documents, applications used, and/or other information from one or more dependent tasks, similar tasks, associated tasks, and/or tasks that are otherwise linked to task 210 ; one or more updates, interactions, and/or events within a given task, project, and/or task-specific workspace; and/or one or more updates, interactions, and/or events within a given task, project, task-specific workspace that occurred while the given user was not in the task-specific workspace and/or working on the given task, and/or other information.
- user information e.g., historical user information, user preferences, etc.
- task information e.g., a type of task, the task title, the task due date, etc.
- FIG. 2 C illustrates an exemplary task-specific workspace, in accordance with one or more implementations.
- Task-specific workspace 216 may include a first set of applications 218 that are accessible via task-specific workspace 216 .
- Window 220 may correspond with one of the applications in the first set of applications 218 .
- Task-specific workspace 216 may include a header 217 .
- Header 217 may include task information describing task 210 .
- Header 217 may include one or more buttons.
- Status button 222 may be used by the user to indicate task 210 is complete and/or incomplete, and/or trigger completion of task 210 .
- Pause button 224 may be used to pause task 210 and/or a timer associated with task 210 .
- Chat button 226 may be used to initiate a chat session related to task 210 and/or make a comment on task 210 .
- Header 217 may display the due date 212 of task 210 .
- header 217 may display a quantity of tasks waiting 216 (e.g., lower priority tasks and/or tasks not presently selected by the user). Header 217 may indicate what a user should be working on such that the user remains focused on task 210 .
- FIG. 2 D illustrates an exemplary graphical user interface for pausing a task-specific workspace, in accordance with one or more implementations.
- Graphical user interface (GUI) 228 may be presented to the user responsive to the user selecting the pause button 224 (see e.g., FIG. 2 C ).
- GUI 228 may present an option to save and/or store the first task-specific workspace and/or the interactions of the first user with first set of applications 218 within the first task-specific workspace 216 .
- GUI 228 may present a notification 230 of the interactions in the task-specific workspace it is saving.
- GUI 228 may include options 232 to send one or more notifications based on progress of the user in the task to one or more interested parties (e.g., followers, team members, dependent task assignees, and/or other interested parties.
- the one or more interested parties may be defined by the environment state information.
- first set of applications 218 may be restored based on the environment state information.
- the exemplary task-specific workspace as illustrated in FIG. 2 C may be presented to the first user. As such, the individual application of first set of applications 218 and its corresponding window 220 may be restored based on the environment state information.
- One or more other applications in first set of applications 218 may also be restored as open, but the windows may be minimized and/or behind window 220 because the interactions of the user when the user paused the task 210 indicated the workspace state (e.g., including the application state and/or window state) illustrated in FIG. 2 C .
- the workspace state e.g., including the application state and/or window state
- one or more servers 102 , one or more client computing platforms 124 , and/or external resource(s) 122 may be operatively linked via one or more electronic communication links.
- electronic communication links may be established, at least in part, via a network 132 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which one or more servers 102 , one or more client computing platforms 124 , and/or external resource(s) 122 , may be operatively linked via some other communication media.
- the external resource(s) 122 may include sources of information, external entities participating with system 100 , and/or other resources. In some implementations, some or all of the functionality attributed herein to external resource(s) 122 may be provided by resources included in system 100 .
- the one or more servers 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of one or more servers 102 in FIG. 1 is not intended to be limiting.
- One or more servers 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to one or more servers 102 .
- one or more servers 102 may be implemented by a cloud of computing platforms operating together as one or more servers 102 .
- Processor(s) 104 and/or processor(s) 105 may be configured to provide information processing capabilities in one or more servers 102 .
- processor(s) 104 and/or processor(s) 105 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information.
- processor(s) 104 and/or processor(s) 105 are shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 104 and/or processor(s) 105 may include a plurality of processing units.
- processor(s) 104 and/or processor(s) 105 may represent processing functionality of a plurality of devices operating in coordination.
- the processor(s) 104 and/or processor(s) 105 may be configured to execute computer readable instruction components 108 , 110 , 112 , 114 , 116 , 118 , and/or other components.
- the processor(s) 104 and/or processor(s) 105 may be configured to execute components 108 , 110 , 112 , 114 , 116 , 118 , and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 104 and/or processor(s) 105 .
- components 108 and/or components 110 , 112 , 114 , 116 , and/or 118 are illustrated in FIG. 1 as being co-located within a single processing unit, in implementations in which processor(s) 104 and/or processor(s) 105 include multiple processing units, one or more of components 108 , 110 , 112 , 114 , 116 , and/or 118 may be located remotely from the other components.
- components 108 , 110 , 112 , 114 , 116 , and/or 118 described herein is for illustrative purposes, and is not intended to be limiting, as any of components 108 , 110 , 112 , 114 , 116 , and/or 118 may provide more or less functionality than is described.
- one or more of components 108 , 110 , 112 , 114 , 116 , and/or 118 may be eliminated, and some or all of its functionality may be provided by other ones of components 108 , 110 , 112 , 114 , 116 , and/or 118 .
- processor(s) 104 and/or processor(s) 105 may be configured to execute one or more additional components that may perform some or all of the functionality attributed herein to one of components 108 , 110 , 112 , 114 , 116 , and/or 118 .
- FIG. 3 illustrates a method 300 for facilitating task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations.
- the operations of method 300 presented below are intended to be illustrative. In some implementations, method 300 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 300 are illustrated in FIG. 3 and described below is not intended to be limiting.
- method 300 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information).
- the one or more processing devices may include one or more devices executing some or all of the operations of method 300 in response to instructions stored electronically on an electronic storage medium.
- the one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 300 .
- presentation of a collaboration environment may be effectuated based on environment state information.
- the environment state information may include user records, project records, task records, and/or other records.
- the environment state information may define a state of the collaboration environment.
- the state of the collaboration environment may include a user state, a project state, a task state, and/or other states.
- the user state may be defined by the user records.
- the user records may define values of user parameters associated with users interacting with and/or viewing the collaboration environment.
- the project state may be defined by the project records.
- the project records may define values of project parameters for projects managed within the collaboration environment.
- the task state may be defined by the task records.
- the task records may define values of task parameters for tasks created and/or assigned within the collaboration environment.
- operation 302 is performed by a collaboration environment component the same as or similar to collaboration environment component 110 (shown in FIG. 1 and described herein).
- operation 304 task-specific workspaces for individual ones of the users for individual ones of the tasks may be facilitated.
- a first task-specific workspace for a first user may be facilitated on a first client computing platform.
- operation 304 is performed by a collaboration environment component the same as or similar to collaboration environment component 110 (shown in FIG. 1 and described herein).
- operation 306 user input indicating selection of a first task may be received.
- operation 306 is performed by a user task component the same as or similar to user task component 112 (shown in FIG. 1 and described herein).
- presentation of the first task may be effectuated for the first user based on the environment state information.
- operation 308 is performed by a user task component the same as or similar to user task component 112 (shown in FIG. 1 and described herein).
- presentation of the first task-specific workspace may be effectuated for the first task.
- a first set of applications may be accessible via the task-specific workspace.
- the first set of applications may have one or more corresponding windows through which the first user interacts with the first set of applications.
- operation 310 is performed by a workspace component the same as or similar to workspace component 116 (shown in FIG. 1 and described herein).
- operation 312 user input indicating a pause and/or completion of the first task may be received.
- the pause and/or completion of the first task may be at a first time.
- operation 312 is performed by a workspace component the same as or similar to workspace component 116 (shown in FIG. 1 and described herein).
- operation 314 information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near the first time may be obtained.
- operation 314 is performed by an application component the same as or similar to application component 118 (shown in FIG. 1 and described herein).
- the information characterizing the interactions of the first user with the first set of applications at or near the first time may be stored.
- the information may be stored as part of a first user record and/or a first task record.
- operation 316 is performed by an application component the same as or similar to application component 118 (shown in FIG. 1 and described herein).
- operation 318 the one or more windows corresponding to the first set of applications for the first task may be minimized and/or closed.
- operation 318 is performed by a workspace component the same as or similar to workspace component 116 (shown in FIG. 1 and described herein).
- the first set of applications may be restored based on the environment state information.
- the first set of applications may be restored responsive to receiving information indicating re-selection of the first task and/or a re-start of the first task. Such that he one or more windows corresponding to the first set of applications may be restored based on the first user record and/or the first task record.
- operation 320 is performed by a workspace component the same as or similar to workspace component 116 (shown in FIG. 1 and described herein).
Abstract
Described herein are systems and methods to facilitate task-specific workspaces for a collaboration work management platform. Task-specific workspaces for individual ones of the users for individual ones of the tasks may be facilitated. Presentation of the first task and/or the first task-specific workspace for the first task for the first user may be effectuated. Information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near a first time may be obtained and/or stored responsive to a pause and/or completion of the first task at the first time. The one or more windows corresponding to the first set of applications for the first task may be minimized and/or closed. Responsive to a re-start of the first task, the first set of applications may be restored based on the environment state information.
Description
- The disclosure relates to systems and methods to facilitate task-specific workspaces for a collaboration work management platform.
- Generic computer interfaces offer few if any options for limiting distractions. Employees often lose time, efficiency, and/or focus because of interruptions, distractions, switching between tasks and losing their place/train of thought, etc. Existing interfaces fail to offer clean workspaces that enable a user to transition between tasks efficiently, without losing their work and/or place. Existing management platforms and/or interfaces often offer too many choices and/or options that make it difficult to actually get work done because users are overwhelmed and/or distracted by the interface.
- The disclosure relates to systems and methods configured to facilitate task-specific workspaces for a collaboration work management platform. The task-specific workspaces may provide a focused workspace in which users can work with fewer distractions. The applications and/or windows open within the task-specific workspace may be related to and/or used for working on a specific task such that users are not distracted by windows and/or applications that are unrelated to the task they are currently working on. When the users pause the task within the task specific workspace and/or switch tasks, the state of the task-specific workspace and/or the user’s interactions with the windows and/or applications within the task-specific workspace may be saved. As such, the user may be able to return to where they left off within the task-specific workspace at a later time. By way of non-limiting example, if a user pauses a task within a task-specific workspace while working within a word document, an internet browser, and/or a presentation application, the state of the word document, the internet browser, and/or the presentation application may be saved such that when the user re-starts and/or re-selects the task, the applications and/or windows corresponding to the word document, the internet browser, and/or the presentation application automatically open. The applications and/or windows corresponding to the word document, internet browser, and/or presentation application may automatically open in the same arrangement and/or to the same section of the word document, internet webpage, and/or slide the user was working on at or near the time they paused the task and/or switched tasks.
- The task-specific workspaces may takeover a desktop of a user. The user may be presented with one or more tasks (e.g., a task list, etc.) rather than all of the different applications and/or documents that are typically presented with existing desktops. This may clutter the desktop, overwhelm the user, and/or distract the user from the tasks they need to complete. Users often work from various different devices (e.g., multiple computers, mobile devices, etc.) having to save things locally and/or transfer them from one device to another. Task-specific workspaces automatically track and maintain the state of the workspace such they the user could pick up where they previously left off on the same device and/or across different devices. This reduces the need to save things locally on devices, eliminates extra steps of uploading saved documents to a file-share program and/or emailing saved documents, and solves the problems associated with lost time getting users up to speed and/or picking up where they left off.
- The presentation of the collaboration environment may be based on environment state information. The storage component may be configured to effectuate storage of the environmental state information. The environmental state information may define the state of the collaboration environment. The state of the collaboration environment may comprise a user state, a project state, a task state, and/or or other states that make up the collaboration environment state. The environmental state information may include one or more records. The one or more records may include one or more user records, project records, task records, and/or other records. The user state may be defined by one or more of the user records. The user records may define values of user parameters associated with users interacting with, viewing, and/or able to interact with or view the collaboration environment. The project state may be defined by the project records. The project records may define values of project parameters for projects managed within the collaboration environment. The task state may be defined by the task record. The task record may define values of task parameters for tasks created and/or assigned within the collaboration environment.
- In some implementations, a system configured to facilitate task-specific workspaces for a collaboration work management platform may include one or more of: one or more servers, one or more client computing platforms, and/or other components. The one or more servers may be configured to communicate with one or more client computing platforms according to a client/server architecture and/or other architecture. The one or more servers and/or client computing platforms may include one or more physical processors configured to execute one or more computer program components. The computer program components may include one or more of an environment state component, a collaboration environment component, a user task component, a desktop component, a workspace component, an application component, and/or other components.
- The one or more client computing platform(s) may be configured to facilitate task-specific workspaces for individual ones of the users for individual tasks. The one or more tasks may include action items, to-do items, and/or objectives within a given project managed via the collaboration work management platform. The one or more tasks may be assigned to one or more users such that the one or more tasks assigned to a given user may appear on a given user’s task list within the collaboration environment.
- User task component may be configured to receive user input indicating selection of a first task. User task component may be configured to effectuate presentation of the first task for the first user. Presentation of the first task for the first user may be based on the environment state information. Responsive to the first user selecting the first task, the user task component may be configured to request information associated with the first task (e.g., a first user record, a first project record, a first task record, and/or other information) from the server. The server may effectuate transmission of the first user record, the first project record, the first task record, and/or other records over the network to the user task component.
- In some implementations, desktop component may be configured to clear the current desktop of a given client computing platform. The desktop may be cleared to initiate a clean workspace (e.g., a first task-specific workspace) for the first task.
- The workspace component may be configured to effectuate presentation of the first task-specific workspace for the first task. In some implementations, a first set of applications may be accessible by the first user via the first task-specific workspace. The first set of applications may have one or more corresponding windows through which the first user interacts with the first set of applications. The first user may work on the first task using one or more applications in the first set of applications.
- The workspace component may be configured to block and/or restrict one or more applications within the task-specific workspace. As such, one or more other applications generally available via the first client computing platform outside of the task-specific workspace, may not accessible within the first task-specific workspace.
- The workspace component may be configured to receive user input indicating a pause and/or completion of the first task at a first time. By way of example, a pause of the first task may be indicated by switching to a second task and/or another task. The application component may be configured to obtain information characterizing interactions of the users with the applications within the task-specific workspaces at or near the time the task is paused. In some implementations, the application component may be configured to obtain information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near the first time. The interactions may include, for example, information indicating which applications the user had open, which webpage(s) and/or file(s) the user had open, the application and/or document titles the user was working on and/or had open, progress information characterizing progress of the first user within the first set of applications (e.g., where the user left off in one or more webpages and/or files), and/or on the first task (e.g., the user paused the task when 60% completed), an amount of time spent on active applications and/or webpages, and/or other interactions.
- The application component may be configured to store the information characterizing the interactions of the first user with the first set of applications at or near the first time. The information characterizing the interactions of the first user with the first set of applications at or near the first time may be stored as part of a first user record and/or a first task record. The workspace component may be configured to minimize and/or close the one or more windows corresponding to the first set of applications for the first task responsive to the receiving the user input indicating the first task is paused and/or completed.
- Responsive to a user re-opening and/or re-starting the first task and/or the first task-specific workspace, the workspace component may be configured to restore the first set of applications based on the environment state information. The first set of applications and/or the one or more windows corresponding to the first set of applications may be restored (e.g., re-opened, re-arranged, reverted, etc.) based on the first user record and/or the first task record.
- These and other objects, features, and characteristics of the system and/or method disclosed herein, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
-
FIG. 1 illustrates a system configured to facilitate task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations. -
FIG. 2A illustrates an exemplary graphical user interface for initiating a task-specific workspace, in accordance with one or more implementations. -
FIG. 2B illustrates an exemplary application recommendation interface for a task-specific workspace, in accordance with one or more implementations. -
FIG. 2C illustrates an exemplary task-specific workspace, in accordance with one or more implementations. -
FIG. 2D illustrates an exemplary graphical user interface for pausing a task-specific workspace, in accordance with one or more implementations. -
FIG. 3 illustrates a method to facilitate task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations. -
FIG. 1 illustrates asystem 100 configured to facilitate task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations. In some implementations,system 100 may be configured to effectuate presentation of a collaboration environment based on environment state information. Users may view and/or interact with the collaboration environment. One or more projects may be managed within the collaboration environment. One more tasks may be created and/or assigned to one or more users within the collaboration environment. - The presentation of the collaboration environment may be based on environment state information. The environment state information may include user records 128, project records 130, task records 132, and/or other records. The environment state information may be continuously generated and/or updated based on the state of the collaboration environment representing the users’ interactions with the collaboration environment. The state of the collaboration environment may include a user state, a project state, a task state, and/or other states. The user state may be defined by user records 128. User records 128 may define values of user parameters associated with users interacting with and/or viewing the collaboration environment. The project state may be defined by project records 130.
Project records 130 may define values of project parameters for projects managed within the collaboration environment. The task state may be defined by task records 132. Task records 132 may define values of task parameters for tasks created and/or assigned within the collaboration environment. - The user parameters associated with the users interacting with and/or viewing the collaboration environment may include parameters describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user interacting with and/or viewing the collaboration environment.
- The user parameters may, by way of non-limiting example, include one or more of: a user name, a user role, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more projects (which may include project parameters defined by one or more project records); one or more tasks (which may include one or more task parameters defined by one or more task records), one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, etc.), one or more authorized applications, one or more presence/interaction parameters (e.g., indicating presence and/or interaction level at an environment level, project level, task all, application level, etc.), one or more notification settings, one or more progress parameters, status information for one or more tasks the user is associated with, one or more statistics related to a given user (e.g., how many tasks the user has completed, how quickly the user completed the tasks, the efficiency of the user, bandwidth of the user, activity level of the user, etc.), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, other user parameters for the given user, and/or other user parameters, project parameters, and/or task parameters for one or more projects and/or tasks the given user is associated with.
- The project parameters for projects managed within the collaboration environment may include parameters describing one or more projects managed within the collaboration environment and/or via the collaboration work management platform, and/or the metadata associated with the one or more projects. Individual ones of the projects may be associated with individual ones of the project records. A project record may define values of the project parameters associated with a given project managed within the collaboration environment and/or via the collaboration work management platform. A given project may have one or more owners and/or one or more team members working on the given project. The given project may include one or more tasks assigned to one or more users under the given project heading.
- The project parameters may, by way of non-limiting example, include one or more of: one or more tasks within individual ones of the projects (which may include task parameters defined by one or more task records), one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), a project name, a project description, one or more project dates (e.g., a start date, a due date, a completion date, and/or other project dates), one or more project members (e.g., an owner, one or more other project members, member access information, and/or other project members and/or member information), a status and/or progress (e.g., an update, a hardcoded status update, a measured status, quantity of tasks remaining in a given project, completed tasks in a given project, and/or other status parameter), one or more attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of tasks within the given project, state of a workspace for a given task within the given project, other project parameters for the given project, and/or other project parameters, user parameters, and/or task parameters for one or more users and/or tasks the given project is associated with.
- The task parameters for tasks within the collaboration environment may include parameters describing one or more tasks created and/or assigned within the collaboration environment and/or via the collaboration work management platform, and/or the metadata associated with the one or more tasks. Individual ones of the tasks may be associated with individual ones of the tasks records. A task record may define values of the task parameters associated with a given task created and/or assigned within the collaboration environment and or via the collaboration work management platform. The tasks make include one or more to-do items, action items, objectives, and/or other tasks one or more users should and/or plan on accomplishing. Tasks may be created by a given user for the given user and/or created by the given user and assigned to one or more other users.
- The task parameters may, by way of non-limiting example, include one or more of: a task name, a task a description, a task status (e.g., complete, incomplete, and/or another status), an assignee, one or more followers, one or more team members, one or more task dates (e.g., a start date, a completion date, a due date, and/or other dates), one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), task upvotes, other hard-coded task responses, one or more tags, one or more custom fields (e.g., priority, cost, stages, and/or other custom fields), one or more dependencies (e.g., tasks dependent on, dependent tasks. Users assigned to dependent tasks, notification settings for dependent tasks, and/or other dependencies), a task URL, one or more subtasks and/or subtask parameters (e.g., name, description, hardcoded status, assignees, due date, state date, comments, upvotes, tags, and/or other subtask parameters), one or more attachments, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), state of a workspace for a given task (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a given task), other task parameters for the given task, and/or other task parameters, user parameters, and/or project parameters for one or more users and/or project(s) the given task is associated with.
- It is noted that any metadata and/or values of parameters related to any users, projects, and/or tasks may be considered values of user parameters, project parameters, and/or task parameters. The terms “user parameters”, “project parameters”, and/or “task parameters” may be used interchangeably herein.
- As is illustrated in
FIG. 1 ,system 100 may include one or more of: one ormore servers 102, one or moreclient computing platforms 124,external resources 122, and/or other components. Users may interact withsystem 100 via one or moreclient computing platforms 124. The one ormore servers 102 may be configured to communicate with one or moreclient computing platforms 124 according to a client/server architecture and/or other communication schemes. The one or moreclient computing platforms 124 may include one or more of a cellular telephone, a smartphone, a digital camera, a laptop, a tablet computer, a desktop computer, a television set-top box, smart TV, a gaming console, and/or other client computing platforms. - The one or
more servers 102 may include one or morephysical processors 104 and/or physical processors 105 (also referred to herein as “one or more processors” and/or “processor(s)”), non-transitoryelectronic storage 126, and/or other components. Non-transitoryelectronic storage 126 may include one or more records. The one or more records may store the environment state information that defines the state of the collaboration environment. The state of the collaboration environment may include a user state, a project state, a task state, and/or other states. The records may include user records 128, project records 130, task records 132, and/or other records. The one or morephysical processors 104 may be configured to access one or more of user records 128, project records 130, task records 132, and/or other records to effectuate transmission of the environment state information overnetwork 132 to client computing platform(s) 124. Client computing platform(s) 124 may use the environment state information to effectuate presentation of the collaboration environment via client computing platform(s) 124. The one or morephysical processors 104 and/orphysical processors 105 may be configured to execute machine-readable instructions 106 and/or machine-readable instructions 107. The machine-readable instructions 106 may include one or more computer program components. The computer program components may include one or more of anenvironment state component 108, acollaboration environment component 110, a user task component 112, adesktop component 114, aworkspace component 116, anapplication component 118, a and/or other components. - In some implementations, server(s) 102 may be configured to provide remote hosting of the features and/or functions of machine-
readable instructions 106 to one or more client computing platform(s) 124 that may be remotely located from server(s) 102. In some implementations, one or more features and/or functions of server(s) 102 may be attributed as local features and/or functions of one or more client computing platform(s) 124. For example, individual ones of the client computing platform(s) 124 may include one or more additional machine-readable instructions 107 comprising the same or similar components as machine-readable instructions 106 of server(s) 102. The client computing platform(s) 124 may be configured to locally execute the one or more components that may be the same or similar to the machine-readable instructions 106. One or more features and/or functions of machine-readable instructions 106 of server(s) 102 may be provided, at least in part, as an application program that may be executed at a givenclient computing platform 124. One or more features and/or functions of machine-readable instructions 107 may be provided, at least in part, at a server(s) 102. - The
electronic storage 126 may include electronic storage media that electronically stores information. The electronic storage media ofelectronic storage 126 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with one ormore servers 102 and/or removable storage that is removably connected to one ormore servers 102. The connection may be facilitated by, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Theelectronic storage 126 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Theelectronic storage 126 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Theelectronic storage 126 may store software algorithms, information determined by processor(s) 104, information received by one ormore servers 102, information received byclient computing platforms 124, and/or other information that enables one ormore servers 102 to function as described herein. - The
electronic storage 126 may be configured to store one or more records and/or information. The one or more records may include one or more of user records 128, project records 130, task records 132, and/or other records. - The one or more records (e.g., user records 128, project records 130, task records 132, and/or other records) may specify and or define values for one or more user parameters, project parameters, and/or other parameters for the collaboration environment. The one or more records may specify correspondences between one or more of the user records 128, project records 130, task records 132, and/or other records. The correspondences may be used to determine which user parameters and/or values, project parameters and/or values, and/or task parameters and/or values are associated with a given user, project, and/or task within the collaboration environment.
- The client computing platform(s) 124 may monitor, and/or collect information for transmission to the one or more server(s) 102 to be stored as environment state information. The client computing platform(s) 124 may obtain and/or collect environment state information from the one or more server(s) 102.
- The
environment state component 108 of machine-readable instructions 106 may be configured to effectuate transmission of the environment state information to client computing platform(s) 124, and/or vice versa. In some implementations,environment state component 108 may be configured to receive information overnetwork 132 from client computing platforms(s) 124.Environment state component 108 may be configured to effectuate storage of the received information as environment state information to one or more user records 128, project records 130, task records 132, and/or other records.Environment state component 108 may be configured to obtain one or more user records 128, project records 130, task records 132, and/or other records in response to and/or based on one or more requests from client computing platform(s) 124.Environment state component 108 may be configured to effectuate transmission of values for user parameters, values for project parameters, values for task parameters, and/or other state information to client computing platform(s) 124. The values for user parameters, values for project parameters, values for task parameters, and/or other state information may be used to effectuate presentation of the relevant tasks and/or projects for a given user of the collaboration environment associated with the givenclient computing platform 124 to which the values and/or other state information is transmitted. -
Collaboration environment component 110 of machine-readable instructions 107 may be configured to effectuate presentation of a collaboration environment. Presentation of the collaboration environment may be based on environment state information. The environment state information may include user records, project records, task records, and/or other records. The environment state information may define a state of the collaboration environment. The state of the collaboration environment may include a user state, a project state, a task state, and/or other states. The user state may be defined by the user records. The user records may define values of user parameters associated with users interacting with and/or viewing the collaboration environment. The project state may be defined by the project records. The project records may define values of project parameters for projects managed within the collaboration environment. The task state may be defined by the task records. The task records may define values of task parameters for tasks created and/or assigned within the collaboration environment. - The client computing platform(s) 124 may effectuate presentation of the collaboration environment. The collaboration environment may include the environment in which users interact with and/or view the one or more tasks and/or projects managed via the collaboration work management platform. The collaboration environment may exist whether or not a given user is viewing and/or interacting with the collaboration environment. In some implementations, projects managed vie the collaboration environment may include one or more tasks. By way of non-limiting example, the one or more tasks may include action items, to-do items, and/or objectives within a given project. The one or more tasks may be assigned to one or more users such that the one or more tasks assigned to a given user may appear on a given user’s task list within the collaboration environment. The one or more client computing platform(s) 124 may be configured to facilitate task-specific workspaces for individual ones of the users for individual ones of the tasks.
- User task component 112 may be configured to receive user input indicating selection of a task. In some implementations, wherein a first task-specific workspace is facilitated for a first user on a first client computing platform, the user input may indicate selection of a first task. User input may include any input and/or indication by a user to start and/or work on the first task. In some implementations, user task component 112 may effectuate presentation of multiple tasks associated with the first user (e.g., assigned to the first user). User task component 112 may be configured to obtain user input indicating a selection of the first task from the multiple tasks.
- In some implementations, user task component 112 may be configured to determine a recommended task (e.g., which task a user should work on) based on the environment state information. The recommended task may be determined, for example, based on the due date, one or more dependencies of the recommended tasks, efficiency and/or time information associated with the given user and/or task (e.g., it is 3 pm and task one is predicted to take the user 2 hours to complete while task two is predicted to take the user 4 hours to complete, the first task may be recommended if, for example, the user typically becomes inactive in the collaboration environment after 5:00 p.m.), one or more other tasks associated with the given user (e.g., the user has 4 other tasks due tomorrow), and/or other information.
- In some implementations, user task component 112 may be configured to determine and/or effectuate presentation of one or more recommended applications, documents, updates, and/or other information for working on the first task. The one or more recommended applications, documents, updates, and/or other information may be presented and/or determined responsive to receiving user input indicating selection of the first task. The one or more recommended applications may be determined based on user information (e.g., historical user information, user preferences, etc.); task information (e.g., a type of task, the task title, the task due date, etc.); generated work, documents, applications used, and/or other information from one or more dependent tasks, similar tasks, associated tasks, and/or tasks that are otherwise linked to task; one or more updates, interactions, and/or events within a given task, project, and/or task-specific workspace; and/or one or more updates, interactions, and/or events within a given task, project, task-specific workspace that occurred while the given user was not in the task-specific workspace and/or working on the given task, and/or other information. The one or more documents, updates, and/or other information may be determined based on other generated work, documents, applications, and/or other information from one or more dependent tasks, similar tasks, associated tasks, and/or tasks that are otherwise linked. In some implementations, user task component 112 may be configured to determine and/or effectuate presentation of one or more recommended applications, documents, updates, and/or other information based on one or more updates, interactions, and/or events within a given task, project, and/or task-specific workspace that occurred while the given user was not in the task-specific workspace and/or working on the given task. As such, the state of a given task-specific workspace may be maintained while a user is not working on the given task and/or within the given task-specific workspace.
- User task component 112 may be configured to effectuate presentation of the first task for the first user based on the environment state information. Responsive to the first user selecting the first task, user task component 112 may be configured to request information associated with the first task from
environment state component 108. Information associated with the first task may include user state information associated with the first user (e.g., the first user record), project state information associated with a first project (e.g., the first project record) under which the first task may be assigned to the first user, task state information associated with the first task (e.g., the first task record), and/or other information. User task component 112 may be configured to receive the environment state information associated with the first task such that the first task may be presented to the first user. - In some implementations,
desktop component 114 may be configured to clear the current desktop of a givenclient computing platform 124.Desktop component 114 may be configured to clear the current desktop to initiate the first task-specific workspace for the first task. The current desktop may be cleared by minimizing and/or closing one or more open applications and/or windows displayed on the current desktop.Desktop component 114 may be configured to clear the current desktop responsive to the current desktop including one or more open applications or windows, and/or responsive to user task component 112 receiving user input receiving user input indicating selection of a first task. -
Workspace component 116 may be configured to effectuate presentation of the first task-specific workspace for the first task. In some implementations, the first task specific workspace may include a task header bar including one or more of a task name and/or an indication of the first task that the user is working on within the first task-specific workspace, a project the task is associated with, a due date, a timer button (e.g., for timing how long a user works on a given task), a status button (e.g., for indicating when a task is complete), a chat and/or message button (e.g., for initiating a comment and/or chat session re the first task, and/or other information. - One or more applications may be available via the task-specific workspace. The user may use the one or more applications while working on the given task associated with the task-specific workspace. By way of non-limiting example, the applications may include: one or more internet applications (e.g., Internet Explorer, Chrome, etc.), one or more document applications (e.g., Microsoft Word, Pages, Adobe Acrobat, Writer, etc.), one or more presentation applications (e.g., PowerPoint, Keynote, etc.), one or more email applications (e.g., Outlook, Gmail, Yahoo mail, etc.), one or more messaging applications (e.g., Slack, Skype, etc.), one or more spreadsheet applications (e.g., Excel, Numbers, etc.), one or more photo/video applications (e.g., photoshop, iPhoto, iMovie, Adobe, Vegas Pro, etc.), and/or other applications (e.g., Genome browser, etc.). In some implementations, a first set of applications may be accessible via the first task-specific workspace. The first set of applications may have one or more corresponding windows through which the first user interacts with the first set of applications.
- The first set of applications may comprise the available applications within the first task-specific workspace. In some implementations, the first set of applications may not include all of the applications accessible via the first-task specific workspace. As such, one or more applications in addition to those from the first set of applications may and/or may not be accessible within the first task-specific workspace. In some implementations, the first set of applications may include one or more applications the first user interacts with while working on the first task within the first task specific workspace.
- In some implementations, one or more other applications generally available via the first client computing platform outside of the task-specific workspace may not be accessible within the first task-specific workspace.
Workspace component 116 may be configured to block and/or restrict one or more applications. In some implementations,workspace component 116 may be configured to determine one or more other applications that are not accessible within the first task-specific workspace.Workspace component 116 may be configured to determine which applications are not accessible based on one or more values for one or more of the user parameters, the project parameters, the task parameters, and/or other parameters indicating the one or more other applications are restricted while the first user is working on the first task via the first task specific workspace. In some implementations, the user parameters, project parameters, task parameters, and/or other parameters indicating the one or more other restricted applications may include task settings and/or user settings indicating which applications to restrict and/or make available for the first task-specific workspace. In some implementations, a user (e.g., the first user, a project and/or task owner, etc.) may determine the user settings. -
Workspace component 116 may be configured to receive user input indicating a pause and/or completion of the first task at a first time. The user input may be received via a pause button within the task-specific workspace. In some implementations, wherein the task-specific workspace has an integrated timer, pausing a task may cause the timer to pause. User input indicating a pause and/or completion of the first task may include switching from one task to another (e.g., via selecting another task). In some implementations, the user input indicating a pause of the first task at the first time may include a selection of a second task. -
Application component 118 may be configured to obtain information characterizing interactions of the users with the applications within the task-specific workspaces at or near the time the task is paused. In some implementations,application component 118 may be configured to obtain information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near the first time. Interactions of the first user with the first set of applications within the first task-specific workspace may include, for example, one or more of information indicating which applications the user had open; which webpages, documents, and/or files the user had open; the application and/or document titles the user was working on and/or had open; progress information characterizing progress of the first user within the first set of applications (e.g., where the user left off in one or more webpages and/or files) and/or on the first task (e.g., the user paused the task when 60% completed), an amount of time spent on active applications, documents, and/or webpages; and/or other interactions. In some implementations,application component 118 may be configured to monitor interactions of the first user with the first set of applications within the first task-specific workspace. The interactions may be monitored until the first time such that the state of the first set of applications at the first time may be obtained. -
Application component 118 may be configured to store the information characterizing the interactions of the first user with the first set of applications at or near the first time as part of a first user record and/or a first task record. In some implementations,application component 118 may be configured to effectuate transmission of the first user record and/or the first task record overnetwork 132 toenvironment state component 108 to store as part of one or more user records 128 and/ortask records 132 inelectronic storage 126. - Returning to
workspace component 116,workspace component 116 may be configured to minimize and/or close the one or more windows corresponding to the first set of applications for the first task. In some implementations, responsive to receiving the user input indicating the pause and/or the completion of the first task,workspace component 116 may be configured to effectuate presentation of an option to save and/or store the first task-specific workspace and/or the interactions of the first user with the first set of applications within the first task-specific workspace. In some implementations, the first-task specific workspace and/or the interactions of the first user with the first set of applications within the first task-specific workspace may be automatically stored responsive to the user pausing the first task, switching tasks, completing the first task and/or otherwise indicating a pause of the first task. In some implementations,workspace component 116 may effectuate presentation of an option to save the task-specific workspace responsive to the user indication the status of the task-specific workspace is complete (e.g., the user changing the status from incomplete to complete). - In some implementations, responsive to receiving the user input indicating the pause and/or the completion of the first task,
workspace component 116 may be configured to effectuate presentation of an option to send a notification based on progress of the first user in the first task to one or more interested parties. The one or more interested parties may be defined by the environment state information. By way of non-limiting example, when the user input indicates the first task is paused (e.g., the user pauses the task and/or switches tasks) and/or completed,workspace component 116 may be configured to effectuate presentation of an option to send a notification indicating the status and/or progress of the task to one or more followers, team-members, dependent task assignees, project owners, dependent task followers and/or team members, and/or other interested parties. -
Workspace component 116 may be configured to restore one of more applications based on the state information responsive to a user re-opining and/or re-starting a task and/or a task-specific workspace. In some implementations, workspace component may be configured to restore the first set of applications based on the environment state information. The first set of applications may be restored byworkspace component 116 responsive to receiving information indicating re-selection of the first task and/or a re-start of the first task. The first set of applications and/or the one or more windows corresponding to the first set of applications may be restored based on the first user record and/or the first task record. As such, for example, the first user may be able to pick up working on the first task where he or she left off (e.g., with the correct applications open, on the right page, etc.). - Re-selecting and/or re-starting a given task may include initiating start of a given task after a user has previously worked on the given task within the given task-specific workspace. In some implementations, the same user and/or a different user may re-start and/or re-select the given task. A different user may re-select and/or re-start the given task and/or the given task-specific workspace even if the user has not previously worked on the given task within the given workspace. In some implementations, if a first user selects and/or initiates the given task-specific workspace, a second user may re-select and/or re-start the given task and/or the given task-specific workspace (e.g., even though the second user may and/or may not have previously worked on the given task and/or within the given task-specific workspace).
- In some implementations, the task-specific workspace may be associated with and/or assigned to a given task (instead of an/or in addition to a given user). As such, the task-specific workspace may be transferable such that another user may be able to pick up working on the task where the first user left off. As such, tasks may be reassigned and/or transferred to other users without losing progress on the task.
- Restoring the first set of applications may include un-minimizing and/or opening the one or more windows corresponding to individual ones of the first set of applications the first user was working on at and/or near the first time. In some implementations, restoring the first set of applications may include un-minimizing, re-opening, arranging, closing, minimizing but opening to the correct page, and/or otherwise restoring the first set of applications and/or corresponding windows to the state they were in at or near the first time. Such that, by way of non-limiting example, responsive to the first user only interacting with one application within the first set of applications at the first time, the one application and/or corresponding window may be restored (e.g., un-minimized, re-opened, closed, minimized but open to the correct page, and/or otherwise restored to the state it was in at or near the first time) when the first user returns to the first task-specific workspace.
- By way of non-limiting example, responsive to the first user interacting with six different applications (four active and two minimized) within the first set of applications at the first time, the four active applications and/or corresponding window may be restored (e.g., un-minimized, re-opened, open to the correct page, and/or otherwise restored to the state they were in at or near the first time) and the two minimized applications and/or corresponding window may be restored (e.g., minimized but loaded to the correct page/location, and/or otherwise restored to the state they were in at or near the first time) when the first user returns to the first task-specific workspace.
- In some implementations, responsive to a user re-starting and/or re-initiating a given task from a different computer than used to previously interact with the task-specific workspace for the given task, restoring one or more of the applications in a given set of applications may include identifying one or more corresponding applications that are similar to the applications previously used within the task specific workspace and/or restoring the one or more corresponding applications. By way of non-limiting example, if the first task-specific workspace is first presented on a first computer and all of the applications within first set of applications are not available on a second computer used to re-start and/or re-initiate the first task, one or more corresponding applications may be restored based on the first environment state information responsive to a given user re-selecting and/or re-starting the first task via the second computer. The one or more corresponding applications may perform the same and/or similar functions as the one or more applications to which they correspond.
- By way of non-limiting example, if the first computer is an Apple computer, the second computer is a PC, and/or one of the applications in the first set of applications is Safari, the corresponding application may include google Chrome on the second computer. In some implementations, user preferences may be taken into account to determine one or more corresponding applications to recommend to a given user. By way of non-limiting example, responsive to internet explorer being present on the first computer and/or both internet explorer and Chrome being present on the second computer,
workspace component 116 may determine Chrome should be recommended (e.g., based on the user records, user preferences, etc.) responsive to a given user re-selecting and/or re-starting the first task via the second computer. - In some implementations,
workspace component 116 may be configured to restore one of more applications based on the state information including one or more interactions and/or updates that occurred while that first user was not working on the first task and/or within the first task-specific workspace. Other users may interact with the first task and/or the first task specific workspace while the first user is not. As such, by way of non-limiting example, if a second user worked on the first task after the first user paused the first task, the interactions and/or progress of the second user on the first task and/or within the first task-specific workspace may be captured within the state information such that when restored by the first user, the interactions and/or progress of the second user may be reflected. In some implementations, the state of the first task and/or the first task-specific workspace may be updated based on user interactions, updates and/or work product by one or more other users and/or interactions, updates, and/or work product from one or more related tasks (e.g., dependent tasks, etc.), projects, and/or other information. - In some implementations, task-specific workspace may include a group workspace that is updated and/or restored according to the state information reflecting interactions and/or progress of one or more users in the group. By way of non-limiting example, some interactions, applications, and/or progress may be user-specific such that the task-specific workspace tracks the state of the task-specific workspace as a whole and/or for individual users within the group of users.
- In some implementations, responsive to a user switching from a first task to a second task,
workspace component 116 may be configured to effectuate presentation of a second task-specific workspace. User task component 112 may be configured to receive user input indicating selection of the second task. The second task may be another task assigned to the first user and/or presented to the first user via the collaboration environment. User task component 112 may effectuate presentation of the second task for the first user based on the environment state information. -
Workspace component 116 may be configured to effectuate presentation of a second task-specific workspace for the second task. A second set of applications may be accessible via the second task-specific workspace. The second set of applications may have one or more corresponding windows through which the first user interacts with the second set of applications. One or more applications in the second set of applications may be different than the applications in the first set of applications. -
Workspace component 116 may be configured to receive user input indicating a pause and/or completion of the second task, and/or a re-selection of the first task and/or another task at a second time.Application component 118 may be configured to obtain information characterizing interactions of the first user with the second set of applications within the second task-specific workspace at or near the second time. -
Application component 118 may be configured to store the information characterizing the interactions of the first user with the second set of applications at or near the second time as a second user record and/or a second task record,Workspace component 116 may be configured to minimize and/or close the one or more windows corresponding to the second set of applications for the second task. -
Workspace component 116 may be configured to restore the second set of applications based on the environment state information. The second set of applications may be restored responsive to responsive to receiving information indicating re-selection of the first task and/or another task, and/or pausing of the second task. The one or more windows corresponding to the second set of applications may be restored based on the second user record and/or the second task record. - By way of non-limiting illustration,
FIG. 2A illustrates an exemplary graphical user interface for initiating a task-specific workspace, in accordance with one or more implementations.Desktop 200 may be presented via a client computing platform the same as or similar to one of client computing platform(s) 124.Desktop 200 may include graphical user interface (GUI) 202.GUI 202 may be configured to effectuate presentation oftask 210 to which the user is assigned.GUI 202 may present a greeting 201, description oftask 210,due date 212,assignee 214, and/or other information associated withtask 210.Greeting 210 may welcome the user and/or indicate how much time the user has to work ontask 210. In some implementations, one or more other tasks may be presented in addition totask 210. By way of non-limiting example,task 210 may be a highest priority task indicated by ahigh priority field 204 based on it having a higher priority than the three other tasks assigned to the user, an earlier due date, one or more dependent tasks, and/or other information.GUI 202 may be presented to the user in order to initiate a task-specific workspace. Responsive to the user clicking onbutton 206 to begintask 210, a task-specific workspace fortask 210 may be initiated. - By way of non-limiting illustration,
FIG. 2B illustrates an exemplary application recommendation interface for a task-specific workspace, in accordance with one or more implementations. In some implementations,application recommendation interface 250 may present one or morerecommended applications 252 fortask 210 responsive to the user selecting and/or initiating work ontask 210.Application recommendation interface 250 may include a “launch all”button 254 that enables the user to launch all of recommendedapplications 252. By way of non-limiting example, one or more of recommendedapplications 252 may be determined based on user information (e.g., historical user information, user preferences, etc.); task information (e.g., a type of task, the task title, the task due date, etc.); generated work, documents, applications used, and/or other information from one or more dependent tasks, similar tasks, associated tasks, and/or tasks that are otherwise linked totask 210; one or more updates, interactions, and/or events within a given task, project, and/or task-specific workspace; and/or one or more updates, interactions, and/or events within a given task, project, task-specific workspace that occurred while the given user was not in the task-specific workspace and/or working on the given task, and/or other information. - By way of non-limiting illustration,
FIG. 2C illustrates an exemplary task-specific workspace, in accordance with one or more implementations. Task-specific workspace 216 may include a first set ofapplications 218 that are accessible via task-specific workspace 216.Window 220 may correspond with one of the applications in the first set ofapplications 218. Task-specific workspace 216 may include aheader 217.Header 217 may include taskinformation describing task 210.Header 217 may include one or more buttons.Status button 222 may be used by the user to indicatetask 210 is complete and/or incomplete, and/or trigger completion oftask 210.Pause button 224 may be used to pausetask 210 and/or a timer associated withtask 210.Chat button 226 may be used to initiate a chat session related totask 210 and/or make a comment ontask 210.Header 217 may display thedue date 212 oftask 210. In some implementations,header 217 may display a quantity of tasks waiting 216 (e.g., lower priority tasks and/or tasks not presently selected by the user).Header 217 may indicate what a user should be working on such that the user remains focused ontask 210. - By way of non-limiting illustration,
FIG. 2D illustrates an exemplary graphical user interface for pausing a task-specific workspace, in accordance with one or more implementations. Graphical user interface (GUI) 228 may be presented to the user responsive to the user selecting the pause button 224 (see e.g.,FIG. 2C ). In some implementations, (not pictured)GUI 228 may present an option to save and/or store the first task-specific workspace and/or the interactions of the first user with first set ofapplications 218 within the first task-specific workspace 216. In some implementations,GUI 228 may present anotification 230 of the interactions in the task-specific workspace it is saving.GUI 228 may includeoptions 232 to send one or more notifications based on progress of the user in the task to one or more interested parties (e.g., followers, team members, dependent task assignees, and/or other interested parties. In some implementations, the one or more interested parties may be defined by the environment state information. - Responsive to the first user re-starting and/or re-selecting the first task, first set of
applications 218 may be restored based on the environment state information. In some implementations, responsive to the first user re-starting and/or re-selecting the first task, the exemplary task-specific workspace as illustrated inFIG. 2C may be presented to the first user. As such, the individual application of first set ofapplications 218 and itscorresponding window 220 may be restored based on the environment state information. One or more other applications in first set ofapplications 218 may also be restored as open, but the windows may be minimized and/or behindwindow 220 because the interactions of the user when the user paused thetask 210 indicated the workspace state (e.g., including the application state and/or window state) illustrated inFIG. 2C . - Returning to
FIG. 1 , in some implementations, one ormore servers 102, one or moreclient computing platforms 124, and/or external resource(s) 122, may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via anetwork 132 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which one ormore servers 102, one or moreclient computing platforms 124, and/or external resource(s) 122, may be operatively linked via some other communication media. - The external resource(s) 122 may include sources of information, external entities participating with
system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resource(s) 122 may be provided by resources included insystem 100. - The one or
more servers 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of one ormore servers 102 inFIG. 1 is not intended to be limiting. One ormore servers 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to one ormore servers 102. For example, one ormore servers 102 may be implemented by a cloud of computing platforms operating together as one ormore servers 102. - Processor(s) 104 and/or processor(s) 105 may be configured to provide information processing capabilities in one or
more servers 102. As such, processor(s) 104 and/or processor(s) 105 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 104 and/or processor(s) 105 are shown inFIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 104 and/or processor(s) 105 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 104 and/or processor(s) 105 may represent processing functionality of a plurality of devices operating in coordination. The processor(s) 104 and/or processor(s) 105 may be configured to execute computerreadable instruction components components - It should be appreciated that although
components 108 and/orcomponents FIG. 1 as being co-located within a single processing unit, in implementations in which processor(s) 104 and/or processor(s) 105 include multiple processing units, one or more ofcomponents different components components components components components -
FIG. 3 illustrates amethod 300 for facilitating task-specific workspaces for a collaboration work management platform, in accordance with one or more implementations. The operations ofmethod 300 presented below are intended to be illustrative. In some implementations,method 300 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations ofmethod 300 are illustrated inFIG. 3 and described below is not intended to be limiting. - In some implementations,
method 300 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations ofmethod 300 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations ofmethod 300. - At an
operation 302, presentation of a collaboration environment may be effectuated based on environment state information. The environment state information may include user records, project records, task records, and/or other records. The environment state information may define a state of the collaboration environment. The state of the collaboration environment may include a user state, a project state, a task state, and/or other states. The user state may be defined by the user records. The user records may define values of user parameters associated with users interacting with and/or viewing the collaboration environment. The project state may be defined by the project records. The project records may define values of project parameters for projects managed within the collaboration environment. The task state may be defined by the task records. The task records may define values of task parameters for tasks created and/or assigned within the collaboration environment. In some embodiments,operation 302 is performed by a collaboration environment component the same as or similar to collaboration environment component 110 (shown inFIG. 1 and described herein). - At an
operation 304, task-specific workspaces for individual ones of the users for individual ones of the tasks may be facilitated. A first task-specific workspace for a first user may be facilitated on a first client computing platform. In some embodiments,operation 304 is performed by a collaboration environment component the same as or similar to collaboration environment component 110 (shown inFIG. 1 and described herein). - At an
operation 306, user input indicating selection of a first task may be received. In some embodiments,operation 306 is performed by a user task component the same as or similar to user task component 112 (shown inFIG. 1 and described herein). - At an
operation 308, presentation of the first task may be effectuated for the first user based on the environment state information. In some embodiments,operation 308 is performed by a user task component the same as or similar to user task component 112 (shown inFIG. 1 and described herein). - At an
operation 310, presentation of the first task-specific workspace may be effectuated for the first task. A first set of applications may be accessible via the task-specific workspace. The first set of applications may have one or more corresponding windows through which the first user interacts with the first set of applications. In some embodiments,operation 310 is performed by a workspace component the same as or similar to workspace component 116 (shown inFIG. 1 and described herein). - At an
operation 312, user input indicating a pause and/or completion of the first task may be received. The pause and/or completion of the first task may be at a first time. In some embodiments,operation 312 is performed by a workspace component the same as or similar to workspace component 116 (shown inFIG. 1 and described herein). - At an
operation 314, information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near the first time may be obtained. In some embodiments,operation 314 is performed by an application component the same as or similar to application component 118 (shown inFIG. 1 and described herein). - At an
operation 316, the information characterizing the interactions of the first user with the first set of applications at or near the first time may be stored. The information may be stored as part of a first user record and/or a first task record. In some embodiments,operation 316 is performed by an application component the same as or similar to application component 118 (shown inFIG. 1 and described herein). - At an
operation 318, the one or more windows corresponding to the first set of applications for the first task may be minimized and/or closed. In some embodiments,operation 318 is performed by a workspace component the same as or similar to workspace component 116 (shown inFIG. 1 and described herein). - At an
operation 320, the first set of applications may be restored based on the environment state information. The first set of applications may be restored responsive to receiving information indicating re-selection of the first task and/or a re-start of the first task. Such that he one or more windows corresponding to the first set of applications may be restored based on the first user record and/or the first task record. In some embodiments,operation 320 is performed by a workspace component the same as or similar to workspace component 116 (shown inFIG. 1 and described herein). - Although the system(s) and/or method(s) of this disclosure have been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the disclosure is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present disclosure contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.
Claims (20)
1. A system configured to facilitate task-specific workspaces within a collaboration environment, the system comprising:
one or more physical processors configured by machine-readable instructions to:
manage environment state information maintaining a collaboration environment, the environment state information describing users interacting with and/or viewing the collaboration environment, and describing tasks created within the collaboration environment and assigned within the collaboration environment to the users who are expected to accomplish one or more actions to complete the tasks;
effectuate communication of user interface information defining a user interface of the collaboration environment to a first computing platform associated with a first user, the user interface displaying a first task-specific workspace for a first task previously assigned to the first user and a list of multiple tasks previously assigned to the first user, wherein the first task-specific workspace presents a first application via a first window; and
responsive to obtaining information defining user input into the user interface indicating a pause of the first task via selection of a second task from the list of multiple tasks:
effectuate storage of interaction information characterizing interactions of the first user with the first application in a first task record of the first task; and/or
cause the first window corresponding to the first application to be closed.
2. The system of claim 1 , wherein the one or more physical processors are further configured by the machine-readable instructions to:
clear a current desktop to initiate the first task-specific workspace for the first task.
3. The system of claim 1 , wherein a second application is made inaccessible within the first task-specific workspace.
4. The system of claim 1 , wherein the one or more physical processors are further configured by the machine-readable instructions to:
responsive to receiving restart information indicating a re-start of the first task, restore the first application within the first task-specific workspace.
5. The system of claim 1 , wherein the interaction information characterizing the interactions of the first user with the first application includes progress information characterizing progress of the first user within the first application and/or on the first task.
6. The system of claim 1 , wherein the one or more physical processors are further configured by the machine-readable instructions to close, responsive to receiving the information defining the user input, the first task-specific workspace.
7. The system of claim 1 , wherein the one or more physical processors are further configured by the machine-readable instructions to effectuate presentation of an option to save and/or store the first task-specific workspace and/or the interactions of the first user with the first application.
8. The system of claim 1 , wherein the one or more physical processors are further configured by the machine-readable instructions to effectuate presentation of an option to send a notification based on progress of the first user on the first task to one or more other ones of the users.
9. The system of claim 1 , wherein the one or more physical processors are further configured by the machine-readable instructions to:
responsive to obtaining the information defining the user input into the user interface indicating the pause of the first task via the selection of the second task from the list of multiple tasks, update the user interface information to cause the user interface to display a second task-specific workspace for the second task.
10. The system of claim 1 , wherein displaying the first task-specific workspace for the first task in the user interface is responsive to a selection of the first task from the list of multiple tasks previously assigned to the first user.
11. A method to facilitate task-specific workspaces within a collaboration environment, the method comprising:
managing environment state information maintaining a collaboration environment, the environment state information describing users interacting with and/or viewing the collaboration environment, and describing tasks created within the collaboration environment and assigned within the collaboration environment to the users who are expected to accomplish one or more actions to complete the tasks;
effectuating communication of user interface information defining a user interface of the collaboration environment to a first computing platform associated with a first user, the user interface displaying a first task-specific workspace for a first task previously assigned to the first user and a list of multiple tasks previously assigned to the first user, wherein the first task-specific workspace presents a first application via a first window; and
responsive to obtaining information defining user input into the user interface indicating a pause of the first task via selection of a second task from the list of multiple tasks:
effectuating storage of interaction information characterizing interactions of the first user with the first application in a first task record of the first task; and/or
causing the first window corresponding to the first application to be closed.
12. The method of claim 11 , further comprising clearing a current desktop to initiate the first task-specific workspace for the first task.
13. The method of claim 11 , wherein a second application is made inaccessible within the first task-specific workspace.
14. The method of claim 11 , further comprising responsive to receiving restart information indicating a re-start of the first task, causing the first application to be restored within the first task-specific workspace.
15. The method of claim 11 , wherein the interaction information characterizing the interactions of the first user with the first application includes progress information characterizing progress of the first user within the first application and/or on the first task.
16. The method of claim 11 , further comprising closing, responsive to receiving the information defining the user input, the first task-specific workspace.
17. The method of claim 11 , further comprising effectuating presentation of an option to save and/or store the first task-specific workspace and/or the interactions of the first user with the first application.
18. The method of claim 11 , further comprising effectuating presentation of an option to send a notification based on progress of the first user on the first task to one or more other ones of the users.
19. The method of claim 11 , further comprising responsive to the obtaining the information defining the user input into the user interface indicating the pause of the first task via the selection of the second task from the list of multiple tasks, updating the user interface information to cause the user interface to display a second task-specific workspace for the second task.
20. The method of claim 11 , wherein displaying the first task-specific workspace for the first task in the user interface is responsive to a selection of the first task from the list of multiple tasks previously assigned to the first user.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/305,100 US20230251880A1 (en) | 2018-04-02 | 2023-04-21 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/908,670 US11138021B1 (en) | 2018-04-02 | 2018-04-02 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US17/408,030 US11720378B2 (en) | 2018-04-02 | 2021-08-20 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US18/305,100 US20230251880A1 (en) | 2018-04-02 | 2023-04-21 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/408,030 Continuation US11720378B2 (en) | 2018-04-02 | 2021-08-20 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
Publications (1)
Publication Number | Publication Date |
---|---|
US20230251880A1 true US20230251880A1 (en) | 2023-08-10 |
Family
ID=77923801
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/908,670 Active US11138021B1 (en) | 2018-04-02 | 2018-04-02 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US17/408,030 Active US11720378B2 (en) | 2018-04-02 | 2021-08-20 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US18/305,100 Pending US20230251880A1 (en) | 2018-04-02 | 2023-04-21 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/908,670 Active US11138021B1 (en) | 2018-04-02 | 2018-04-02 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US17/408,030 Active US11720378B2 (en) | 2018-04-02 | 2021-08-20 | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
Country Status (1)
Country | Link |
---|---|
US (3) | US11138021B1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11831457B2 (en) | 2018-06-08 | 2023-11-28 | Asana, Inc. | Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users |
Families Citing this family (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10225352B2 (en) * | 2013-12-20 | 2019-03-05 | Sony Corporation | Work sessions |
US10810222B2 (en) | 2014-11-24 | 2020-10-20 | Asana, Inc. | Continuously scrollable calendar user interface |
US10977434B2 (en) | 2017-07-11 | 2021-04-13 | Asana, Inc. | Database model which provides management of custom fields and methods and apparatus therfor |
US10623359B1 (en) | 2018-02-28 | 2020-04-14 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US11138021B1 (en) | 2018-04-02 | 2021-10-05 | Asana, Inc. | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US10613735B1 (en) | 2018-04-04 | 2020-04-07 | Asana, Inc. | Systems and methods for preloading an amount of content based on user scrolling |
US10616151B1 (en) | 2018-10-17 | 2020-04-07 | Asana, Inc. | Systems and methods for generating and presenting graphical user interfaces |
US10956845B1 (en) | 2018-12-06 | 2021-03-23 | Asana, Inc. | Systems and methods for generating prioritization models and predicting workflow prioritizations |
US11113667B1 (en) | 2018-12-18 | 2021-09-07 | Asana, Inc. | Systems and methods for providing a dashboard for a collaboration work management platform |
US11568366B1 (en) | 2018-12-18 | 2023-01-31 | Asana, Inc. | Systems and methods for generating status requests for units of work |
US10684870B1 (en) * | 2019-01-08 | 2020-06-16 | Asana, Inc. | Systems and methods for determining and presenting a graphical user interface including template metrics |
US11782737B2 (en) | 2019-01-08 | 2023-10-10 | Asana, Inc. | Systems and methods for determining and presenting a graphical user interface including template metrics |
US11204683B1 (en) | 2019-01-09 | 2021-12-21 | Asana, Inc. | Systems and methods for generating and tracking hardcoded communications in a collaboration management platform |
US11341445B1 (en) | 2019-11-14 | 2022-05-24 | Asana, Inc. | Systems and methods to measure and visualize threshold of user workload |
US11783253B1 (en) | 2020-02-11 | 2023-10-10 | Asana, Inc. | Systems and methods to effectuate sets of automated actions outside and/or within a collaboration environment based on trigger events occurring outside and/or within the collaboration environment |
US11599855B1 (en) | 2020-02-14 | 2023-03-07 | Asana, Inc. | Systems and methods to attribute automated actions within a collaboration environment |
US11763259B1 (en) | 2020-02-20 | 2023-09-19 | Asana, Inc. | Systems and methods to generate units of work in a collaboration environment |
WO2021217470A1 (en) * | 2020-04-29 | 2021-11-04 | Citrix Systems, Inc. | Computer resource allocation based on categorizing computing processes |
US11900323B1 (en) | 2020-06-29 | 2024-02-13 | Asana, Inc. | Systems and methods to generate units of work within a collaboration environment based on video dictation |
US11455601B1 (en) | 2020-06-29 | 2022-09-27 | Asana, Inc. | Systems and methods to measure and visualize workload for completing individual units of work |
US11449836B1 (en) | 2020-07-21 | 2022-09-20 | Asana, Inc. | Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment |
US11568339B2 (en) | 2020-08-18 | 2023-01-31 | Asana, Inc. | Systems and methods to characterize units of work based on business objectives |
US11769115B1 (en) | 2020-11-23 | 2023-09-26 | Asana, Inc. | Systems and methods to provide measures of user workload when generating units of work based on chat sessions between users of a collaboration environment |
US11405435B1 (en) | 2020-12-02 | 2022-08-02 | Asana, Inc. | Systems and methods to present views of records in chat sessions between users of a collaboration environment |
JP2022091538A (en) * | 2020-12-09 | 2022-06-21 | 株式会社リコー | Information processing device, request management system, request management method, and program |
US11694162B1 (en) | 2021-04-01 | 2023-07-04 | Asana, Inc. | Systems and methods to recommend templates for project-level graphical user interfaces within a collaboration environment |
US11676107B1 (en) | 2021-04-14 | 2023-06-13 | Asana, Inc. | Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles |
US20220334691A1 (en) * | 2021-04-14 | 2022-10-20 | Microsoft Technology Licensing, Llc | Virtual commute |
US11553045B1 (en) | 2021-04-29 | 2023-01-10 | Asana, Inc. | Systems and methods to automatically update status of projects within a collaboration environment |
US11803814B1 (en) | 2021-05-07 | 2023-10-31 | Asana, Inc. | Systems and methods to facilitate nesting of portfolios within a collaboration environment |
US11792028B1 (en) | 2021-05-13 | 2023-10-17 | Asana, Inc. | Systems and methods to link meetings with units of work of a collaboration environment |
US11809222B1 (en) | 2021-05-24 | 2023-11-07 | Asana, Inc. | Systems and methods to generate units of work within a collaboration environment based on selection of text |
USD999778S1 (en) | 2021-08-12 | 2023-09-26 | Hewlett Packard Enterprise Development Lp | Display with graphical user interface for surfacing action items |
US11756000B2 (en) | 2021-09-08 | 2023-09-12 | Asana, Inc. | Systems and methods to effectuate sets of automated actions within a collaboration environment including embedded third-party content based on trigger events |
US11635884B1 (en) | 2021-10-11 | 2023-04-25 | Asana, Inc. | Systems and methods to provide personalized graphical user interfaces within a collaboration environment |
US11868706B1 (en) * | 2021-12-13 | 2024-01-09 | Notion Labs, Inc. | System, method, and computer program for syncing content across workspace pages |
US11687701B1 (en) | 2022-01-21 | 2023-06-27 | Notion Labs, Inc. | System, method, and computer program for enabling text editing across multiple content blocks in a system |
US11836681B1 (en) | 2022-02-17 | 2023-12-05 | Asana, Inc. | Systems and methods to generate records within a collaboration environment |
US20240004674A1 (en) * | 2022-06-29 | 2024-01-04 | Atlassian Pty Ltd. | Buffering and replaying user interaction event content received at a frontend application while asynchronously loading resources supporting a page from a backend application of a multiuser collaboration tool |
US11863601B1 (en) | 2022-11-18 | 2024-01-02 | Asana, Inc. | Systems and methods to execute branching automation schemes in a collaboration environment |
Family Cites Families (435)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5233687A (en) * | 1987-03-25 | 1993-08-03 | Xerox Corporation | User interface with multiple workspaces for sharing display system objects |
EP0300456A3 (en) | 1987-07-24 | 1990-08-08 | Bruce H. Faaland | Improved scheduling method and system |
CA2054026A1 (en) | 1990-10-31 | 1992-05-01 | William Monroe Turpin | Goal oriented electronic form system |
JPH05197573A (en) | 1991-08-26 | 1993-08-06 | Hewlett Packard Co <Hp> | Task controlling system with task oriented paradigm |
US5623404A (en) | 1994-03-18 | 1997-04-22 | Minnesota Mining And Manufacturing Company | System and method for producing schedules of resource requests having uncertain durations |
US5611076A (en) | 1994-09-21 | 1997-03-11 | Micro Data Base Systems, Inc. | Multi-model database management system engine for databases having complex data models |
US6332147B1 (en) | 1995-11-03 | 2001-12-18 | Xerox Corporation | Computer controlled display system using a graphical replay device to control playback of temporal data representing collaborative activities |
WO1997041819A1 (en) | 1996-05-02 | 1997-11-13 | Les Laboratoires Asana Inc. | Proprioceptive sole or pedal device containing crystals for treatment of statural disorders |
EP0848334A4 (en) * | 1996-07-01 | 2007-08-29 | Fujitsu Ltd | Device and method of controlling intergroup resource utilization |
US5721770A (en) | 1996-07-02 | 1998-02-24 | Lucent Technologies Inc. | Agent vectoring programmably conditionally assigning agents to various tasks including tasks other than handling of waiting calls |
GB2321322B (en) | 1996-10-28 | 2001-10-10 | Altera Corp | Remote software technical support |
US6256651B1 (en) | 1997-06-20 | 2001-07-03 | Raja Tuli | Time management workflow software |
US6292830B1 (en) | 1997-08-08 | 2001-09-18 | Iterations Llc | System for optimizing interaction among agents acting on multiple levels |
US6621505B1 (en) * | 1997-09-30 | 2003-09-16 | Journee Software Corp. | Dynamic process-based enterprise computing system and method |
US7020697B1 (en) | 1999-10-01 | 2006-03-28 | Accenture Llp | Architectures for netcentric computing systems |
US7086062B1 (en) | 1999-10-11 | 2006-08-01 | I2 Technologies Us, Inc. | System and method for handling a unit of work |
US6629081B1 (en) | 1999-12-22 | 2003-09-30 | Accenture Llp | Account settlement and financing in an e-commerce environment |
US6922685B2 (en) | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US6850939B2 (en) | 2000-11-30 | 2005-02-01 | Projectvillage | System and method for providing selective data access and workflow in a network environment |
US20020082889A1 (en) | 2000-12-20 | 2002-06-27 | Electronic Data Systems Corporation | System and method for project management and assessment |
US20020143594A1 (en) | 2000-12-23 | 2002-10-03 | Atub, Inc. | System, method and article of manufacture for alerting a manager of a critical outstanding task |
US7159178B2 (en) | 2001-02-20 | 2007-01-02 | Communispace Corp. | System for supporting a virtual community |
US7330895B1 (en) | 2001-03-15 | 2008-02-12 | Microsoft Corporation | Representation, decision models, and user interface for encoding managing preferences, and performing automated decision making about the timing and modalities of interpersonal communications |
BR0209259B1 (en) | 2001-04-30 | 2011-03-09 | hub. | |
US7418482B1 (en) | 2001-05-17 | 2008-08-26 | Palmsource, Inc. | Web-based task assistants for wireless personal devices |
US7191140B2 (en) | 2001-05-29 | 2007-03-13 | Navitaire, Inc. | Method and system for generating optimal solutions for open pairings through one-way fixes and matching transformations |
US8108241B2 (en) | 2001-07-11 | 2012-01-31 | Shabina Shukoor | System and method for promoting action on visualized changes to information |
US7289966B2 (en) | 2001-08-14 | 2007-10-30 | Norman Ken Ouchi | Method and system for adapting the execution of a workflow route |
US7039904B2 (en) | 2001-08-24 | 2006-05-02 | Sun Microsystems, Inc. | Frameworks for generation of Java macro instructions for storing values into local variables |
US20030097410A1 (en) | 2001-10-04 | 2003-05-22 | Atkins R. Travis | Methodology for enabling multi-party collaboration across a data network |
US6859523B1 (en) | 2001-11-14 | 2005-02-22 | Qgenisys, Inc. | Universal task management system, method and product for automatically managing remote workers, including assessing the work product and workers |
US20030097406A1 (en) | 2001-11-16 | 2003-05-22 | Ben Stafford | Method of exchanging messages |
US20030126001A1 (en) | 2001-12-28 | 2003-07-03 | Margo Northcutt | Process for managing requests for work within an organization through a centralized workflow management system |
US7039596B1 (en) | 2002-01-18 | 2006-05-02 | America Online, Inc. | Calendar overlays |
US6769013B2 (en) | 2002-02-02 | 2004-07-27 | E-Wings, Inc. | Distributed system for interactive collaboration |
US7917855B1 (en) | 2002-04-01 | 2011-03-29 | Symantec Operating Corporation | Method and apparatus for configuring a user interface |
WO2003085525A2 (en) | 2002-04-02 | 2003-10-16 | Collabo-Technology, Inc. | Method and apparatus for synchronous project collaboration |
US6978260B2 (en) | 2002-04-23 | 2005-12-20 | Hewlett-Packard Development Company, L.P. | System and method for storing data |
US7395221B2 (en) | 2002-05-09 | 2008-07-01 | International Business Machines Corporation | Intelligent free-time search |
AU2003239385A1 (en) | 2002-05-10 | 2003-11-11 | Richard R. Reisman | Method and apparatus for browsing using multiple coordinated device |
US20030233265A1 (en) | 2002-06-17 | 2003-12-18 | International Business Machines Corporation | Method, system and program product for interactive electronic meeting scheduling |
US20030233268A1 (en) | 2002-06-17 | 2003-12-18 | Ehsan Taqbeem | Multi-dimensional interdependency based project management |
US8639650B1 (en) | 2003-06-25 | 2014-01-28 | Susan Pierpoint Gill | Profile-responsive system for information exchange in human- and device-adaptive query-response networks for task and crowd management, distributed collaboration and data integration |
US7653562B2 (en) | 2002-07-31 | 2010-01-26 | Sap Aktiengesellschaft | Workflow management architecture |
US7805327B1 (en) | 2002-07-31 | 2010-09-28 | Sap Aktiengesellschaft | Transformations between combined and individual workflows |
US7350188B2 (en) | 2002-07-31 | 2008-03-25 | Sap Aktiengesellschaft | Aggregation of private and shared workflows |
AU2003272486A1 (en) | 2002-09-17 | 2004-04-08 | Bellsouth Intellectual Property Corporation | Client-based message protocol translation |
US20060167736A1 (en) | 2002-10-01 | 2006-07-27 | Weiss Paul F | Schedule chart for project management |
US7346526B2 (en) | 2002-10-16 | 2008-03-18 | Ita Software, Inc. | System and method for entering flexible travel queries with layover description |
TW200407735A (en) | 2002-11-08 | 2004-05-16 | Hon Hai Prec Ind Co Ltd | System and method for controlling task assignment and work schedule of projects |
US20040098291A1 (en) | 2002-11-14 | 2004-05-20 | International Business Machines Corporation | Apparatus and method for visualizing resource consumption |
US7676542B2 (en) | 2002-12-02 | 2010-03-09 | Sap Ag | Establishing a collaboration environment |
US7325198B2 (en) | 2002-12-31 | 2008-01-29 | Fuji Xerox Co., Ltd. | Calendar-based interfaces for browsing and manipulation of digital images |
US7783614B2 (en) | 2003-02-13 | 2010-08-24 | Microsoft Corporation | Linking elements of a document to corresponding fields, queries and/or procedures in a database |
US20040230447A1 (en) | 2003-03-14 | 2004-11-18 | Sven Schwerin-Wenzel | Collaborative workspaces |
DE10315744B4 (en) | 2003-04-04 | 2007-05-31 | Sennheiser Electronic Gmbh & Co. Kg | Microphone with RF transmitter |
EP1639440A4 (en) | 2003-04-25 | 2009-03-11 | Apple Inc | Graphical user interface for browsing, searching and presenting media items |
US8335705B2 (en) | 2003-07-01 | 2012-12-18 | Sap Ag | Managing resources for projects |
US20070041542A1 (en) | 2003-07-14 | 2007-02-22 | Schramm Steven D | Connection management in communications systems |
CN100584183C (en) | 2003-07-18 | 2010-01-20 | 富士机械制造株式会社 | Management apparatus |
US7779039B2 (en) | 2004-04-02 | 2010-08-17 | Salesforce.Com, Inc. | Custom entities and fields in a multi-tenant database system |
US20050137925A1 (en) | 2003-10-23 | 2005-06-23 | Lakritz Kenneth B. | Resource scheduling and monitoring |
WO2005071564A1 (en) | 2004-01-21 | 2005-08-04 | Rnc Global Projects | A project management method and system |
US7349920B1 (en) | 2004-02-13 | 2008-03-25 | Microsoft Corporation | Simultaneous display of multiple calendar systems |
US20050210394A1 (en) | 2004-03-16 | 2005-09-22 | Crandall Evan S | Method for providing concurrent audio-video and audio instant messaging sessions |
JP4177280B2 (en) | 2004-03-25 | 2008-11-05 | 東芝ソリューション株式会社 | Planning work management support system and planning work management support program |
US7370282B2 (en) | 2004-04-06 | 2008-05-06 | Cary James C | Grouping and displaying multiple tasks within an event object of an electronic calendar |
US7640511B1 (en) | 2004-04-29 | 2009-12-29 | Paul Erich Keel | Methods and apparatus for managing and inferring relationships from information objects |
US20060028917A1 (en) | 2004-08-05 | 2006-02-09 | International Business Machines Corp. | Milestone bar calender |
JP4239932B2 (en) | 2004-08-27 | 2009-03-18 | 株式会社日立製作所 | production management system |
US7747966B2 (en) | 2004-09-30 | 2010-06-29 | Microsoft Corporation | User interface for providing task management and calendar information |
US20060085245A1 (en) | 2004-10-19 | 2006-04-20 | Filenet Corporation | Team collaboration system with business process management and records management |
US7519924B2 (en) | 2004-11-03 | 2009-04-14 | Research In Motion Limited | Handheld electronic device including appointment and meeting conflict notification, and associated method |
US8499300B2 (en) | 2004-12-20 | 2013-07-30 | Bank Of America Corporation | System and method for task management of rule based tasks |
US7593992B2 (en) | 2004-12-23 | 2009-09-22 | Sap Ag | Organizer or e-mail and workflow integration |
US20070255674A1 (en) | 2005-01-10 | 2007-11-01 | Instant Information Inc. | Methods and systems for enabling the collaborative management of information based upon user interest |
US20080046471A1 (en) | 2005-02-01 | 2008-02-21 | Moore James F | Calendar Synchronization using Syndicated Data |
EP1913534A4 (en) | 2005-02-11 | 2010-07-07 | Volt Inf Sciences Inc | Project work change in plan/scope administrative and business information synergy system and method |
US7406689B2 (en) | 2005-03-22 | 2008-07-29 | International Business Machines Corporation | Jobstream planner considering network contention & resource availability |
US20060224430A1 (en) | 2005-04-05 | 2006-10-05 | Cisco Technology, Inc. | Agenda based meeting management system, interface and method |
WO2006113717A2 (en) | 2005-04-18 | 2006-10-26 | Poulsen Jay H | Project manager system and method |
JP2007179351A (en) | 2005-12-28 | 2007-07-12 | Sony Corp | File management device and image display device |
EP2247067B1 (en) | 2005-06-09 | 2016-05-11 | Whirlpool Corporation | Appliance with embedded virtual router |
US8417782B2 (en) | 2005-07-14 | 2013-04-09 | Yahoo! Inc. | Universal calendar event handling |
US20070038494A1 (en) | 2005-08-15 | 2007-02-15 | Cognetics Corporation | Team management system and method |
US8103533B2 (en) | 2005-08-26 | 2012-01-24 | United Space Alliance, Llc | Automated resource planning tool and user interface |
JP2007094467A (en) | 2005-09-27 | 2007-04-12 | Hitachi Software Eng Co Ltd | Progress management system |
US8849908B2 (en) | 2005-10-13 | 2014-09-30 | Kaydon A. Stanzione | Internet based data, voice and video alert notification communications system |
US7853467B2 (en) | 2005-10-26 | 2010-12-14 | At&T Intellectual Property Ii, L.P. | Worklist integration of logical and physical tasks |
US10157355B2 (en) | 2005-11-15 | 2018-12-18 | General Electric Company | Method to view schedule interdependencies and provide proactive clinical process decision support in day view form |
US20070143169A1 (en) | 2005-12-21 | 2007-06-21 | Grant Chad W | Real-time workload information scheduling and tracking system and related methods |
US7590413B2 (en) | 2006-04-03 | 2009-09-15 | Research In Motion Limited | Free busy calendar interface |
US20070255715A1 (en) | 2006-04-26 | 2007-11-01 | Bayhub, Inc. | Collaborative hub system for accessing and managing shared business content |
US8886553B2 (en) | 2006-05-02 | 2014-11-11 | Microsoft Corporation | Visual workflow process notation and layout |
EP2076874A4 (en) | 2006-05-13 | 2011-03-09 | Sap Ag | Consistent set of interfaces derived from a business object model |
US9350560B2 (en) | 2006-05-31 | 2016-05-24 | International Business Machines Corporation | Selective information sharing across team spaces |
US20070288283A1 (en) | 2006-06-09 | 2007-12-13 | Devshop Inc. | Method for project management |
US20070294344A1 (en) | 2006-06-14 | 2007-12-20 | Aspect Software | Automatic scheduling system |
US20080126930A1 (en) | 2006-06-28 | 2008-05-29 | Research In Motion Limited | Method and apparatus for dynamically varying one or more properties of a display element in response to variation in an associated characteristic |
US8005705B2 (en) | 2006-09-07 | 2011-08-23 | International Business Machines Corporation | Validating a baseline of a project |
US7904324B2 (en) | 2006-09-28 | 2011-03-08 | International Business Machines Corporation | Method and system for assessing schedule performance issues of a project |
US20080079730A1 (en) | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Character-level font linking |
US20080091782A1 (en) | 2006-10-13 | 2008-04-17 | Gabriel Jakobson | Method and system for delegating and managing tasks over instant messenger |
US20080189638A1 (en) | 2006-10-16 | 2008-08-07 | Invensys Systems, Inc. | Bridging human machine interface technologies in a process automation and information management environment |
US8522240B1 (en) | 2006-10-19 | 2013-08-27 | United Services Automobile Association (Usaa) | Systems and methods for collaborative task management |
US20100169802A1 (en) | 2006-11-08 | 2010-07-01 | Seth Goldstein | Methods and Systems for Storing, Processing and Managing User Click-Stream Data |
US20080155547A1 (en) | 2006-12-22 | 2008-06-26 | Yahoo! Inc. | Transactional calendar |
US7869941B2 (en) | 2006-12-29 | 2011-01-11 | Aol Inc. | Meeting notification and modification service |
KR100724141B1 (en) | 2006-12-29 | 2007-05-31 | 주식회사 네오패드 | Apparatus for Hangul output and method thereof |
US20080221946A1 (en) | 2007-01-05 | 2008-09-11 | Robert Balon | Method and system for evaluating and summarizing weekly project progress |
US20080175104A1 (en) | 2007-01-23 | 2008-07-24 | Microsoft Corporation | Flexible electronic calendar integrating tasks and appointments |
US9213950B2 (en) | 2007-02-09 | 2015-12-15 | Anthony Keith Randell | Method and system for managing a plurality of processes or tasks |
WO2008106060A1 (en) | 2007-02-27 | 2008-09-04 | Ascendent Telecommunications, Inc. | Method, apparatus and system for initiating calendar events |
US7996774B1 (en) | 2007-02-28 | 2011-08-09 | Emc Corporation | Hierarchical display of project information in a collaboration environment |
CA2681355A1 (en) | 2007-03-20 | 2008-09-25 | Tungle Corporation | Method and apparatus for sharing calendar information |
US20080244582A1 (en) | 2007-03-31 | 2008-10-02 | Brown William E | WEB-Based Task Management System and Method |
US20080268876A1 (en) | 2007-04-24 | 2008-10-30 | Natasha Gelfand | Method, Device, Mobile Terminal, and Computer Program Product for a Point of Interest Based Scheme for Improving Mobile Visual Searching Functionalities |
US20080270198A1 (en) | 2007-04-25 | 2008-10-30 | Hewlett-Packard Development Company, L.P. | Systems and Methods for Providing Remediation Recommendations |
US7996744B2 (en) | 2007-04-30 | 2011-08-09 | Nokia Corporation | Method and apparatus for providing a data retransmission scheme |
US20080270240A1 (en) | 2007-04-30 | 2008-10-30 | Viva Chu | Systems and methods of managing tasks assigned to an individual |
US20080281665A1 (en) | 2007-05-08 | 2008-11-13 | Verizon Laboratories, Inc. | Automated Calendar Concierge |
US9230228B2 (en) | 2007-06-12 | 2016-01-05 | International Business Machines Corporation | Method and system for providing a bi-directional feedback loop between project management and personal calendar systems |
US9026409B2 (en) | 2007-08-06 | 2015-05-05 | Design Ready Controls, Inc. | Systems, methods, and software for automated design and manufacturing of HVAC control panels |
US7865384B2 (en) | 2007-08-17 | 2011-01-04 | International Business Machines Corporation | System and method for identifying and reducing costs of information technology actions in real time |
US8095472B2 (en) | 2007-08-20 | 2012-01-10 | Sap Ag | Business object acting as a logically central source for collaboration on objectives |
US9953282B2 (en) | 2007-09-04 | 2018-04-24 | International Business Machines Corporation | System and method for providing automatic task assignment and notification |
US20090076878A1 (en) | 2007-09-19 | 2009-03-19 | Matthias Woerner | Efficient project staffing |
US8645182B2 (en) | 2007-10-02 | 2014-02-04 | International Business Machines Corporation | Integrated calendar and task scheduler |
US8146104B2 (en) | 2007-10-09 | 2012-03-27 | International Business Machines Corporation | System and method for programmatically generating to-do list and creating notification between calendar and other applications |
US8185827B2 (en) | 2007-10-26 | 2012-05-22 | International Business Machines Corporation | Role tailored portal solution integrating near real-time metrics, business logic, online collaboration, and web 2.0 content |
US20100145801A1 (en) | 2007-11-01 | 2010-06-10 | Jagannadha Raju Chekuri | Methods and systems for a time-aware or calendar-aware facilitator to improve utilization of time-sensitive or perishable resources |
US20090133027A1 (en) | 2007-11-21 | 2009-05-21 | Gunning Mark B | Systems and Methods for Project Management Task Prioritization |
US20090167553A1 (en) | 2007-12-30 | 2009-07-02 | Jin Hong | Open Mobile Online Reservation and Ordering Systems |
US20090187454A1 (en) | 2008-01-22 | 2009-07-23 | International Business Machines Corporation | Computer Program Product For Efficient Scheduling Of Meetings |
US20090199192A1 (en) | 2008-02-05 | 2009-08-06 | Robert Laithwaite | Resource scheduling apparatus and method |
WO2009102728A1 (en) | 2008-02-11 | 2009-08-20 | Clearshift Corporation | Online work management system |
US20090204463A1 (en) | 2008-02-13 | 2009-08-13 | Lockheed Martin Corporation | Method, tool, and system for analyzing a project |
US9208262B2 (en) | 2008-02-22 | 2015-12-08 | Accenture Global Services Limited | System for displaying a plurality of associated items in a collaborative environment |
US20090234699A1 (en) | 2008-03-15 | 2009-09-17 | Microsoft Corporation | User Interface For Scheduling Resource Assignments |
US20090241053A1 (en) | 2008-03-21 | 2009-09-24 | Augustine Nancy L | Systems and methods for displaying rolling sequences |
US20130215116A1 (en) | 2008-03-21 | 2013-08-22 | Dressbot, Inc. | System and Method for Collaborative Shopping, Business and Entertainment |
US8019863B2 (en) | 2008-03-28 | 2011-09-13 | Ianywhere Solutions, Inc. | Synchronizing events between mobile devices and servers |
US8276144B2 (en) * | 2008-04-15 | 2012-09-25 | International Business Machines Corporation | Electronic device workspace restriction |
US20090287523A1 (en) | 2008-05-19 | 2009-11-19 | Microsoft Corporation | Showing and correcting irregularities in a schedule |
US8345849B2 (en) | 2008-05-27 | 2013-01-01 | Avaya Inc. | Telecommunications endpoint that prompts a user to focus on a monitored call |
US20090299808A1 (en) | 2008-05-30 | 2009-12-03 | Gilmour Tom S | Method and system for project management |
US8516049B2 (en) | 2008-06-09 | 2013-08-20 | International Business Machines Corporation | Administering instant messaging (‘IM’) chat sessions |
US20100005087A1 (en) | 2008-07-01 | 2010-01-07 | Stephen Basco | Facilitating collaborative searching using semantic contexts associated with information |
US20100070888A1 (en) | 2008-09-13 | 2010-03-18 | Mark Watabe | Device and method for graphical user interface having time based visualization and manipulation of data |
US20100088137A1 (en) | 2008-10-06 | 2010-04-08 | Klaus Weiss | Work lists and cockpit to control complex processes |
US8527287B1 (en) | 2008-10-08 | 2013-09-03 | Intuit Inc. | Method and system for attending a meeting |
US8429540B1 (en) * | 2008-10-10 | 2013-04-23 | Adobe Systems Incorporated | End user created collaborative and non-collaborative workspace application container system and method |
US20100269049A1 (en) | 2008-10-13 | 2010-10-21 | Regen Fearon | System and method for managing events in a multiple schedule environment |
US8788309B2 (en) | 2008-10-23 | 2014-07-22 | International Business Machines Corporation | Application of cost constraints in event scheduling |
US20100115523A1 (en) | 2008-10-30 | 2010-05-06 | International Business Machines Corporation | Method and apparatus for allocating tasks and resources for a project lifecycle |
US9466049B2 (en) | 2008-11-26 | 2016-10-11 | Red Hat, Inc. | Analyzing activity patterns in online communities |
US20100169146A1 (en) | 2008-12-30 | 2010-07-01 | International Business Machines Corporation | Automated scheduling of to-do items within a calendar |
US8341189B2 (en) | 2009-03-31 | 2012-12-25 | Microsoft Corporation | Extending collaboration capabilities to external data |
US8160911B2 (en) | 2009-05-19 | 2012-04-17 | Microsoft Corporation | Project management applications utilizing summary tasks for top-down project planning |
US20110054968A1 (en) | 2009-06-04 | 2011-03-03 | Galaviz Fernando V | Continuous performance improvement system |
US20100313151A1 (en) | 2009-06-04 | 2010-12-09 | Microsoft Corporation | Representing data on configurable timeline with filter |
US8321253B2 (en) | 2009-06-09 | 2012-11-27 | Accenture Global Services Limited | Technician control system |
US20110015961A1 (en) | 2009-07-15 | 2011-01-20 | Danny Chan | Method and system for an event scheduler |
US20110022662A1 (en) | 2009-07-23 | 2011-01-27 | International Business Machines Corporation | Event triggered notifications for collaborative processes |
US20110055177A1 (en) | 2009-08-26 | 2011-03-03 | International Business Machines Corporation | Collaborative content retrieval using calendar task lists |
GB0915863D0 (en) | 2009-09-10 | 2009-10-14 | Smart Overseas Inc | Improvements in or relating to a virtual management system and method |
US8712820B2 (en) | 2009-09-20 | 2014-04-29 | Blackberry Limited | Mobile application for calendar sharing and scheduling |
US20110072372A1 (en) | 2009-09-21 | 2011-03-24 | Research In Motion Limited | Electronic device and method of controlling the same for determination of free time periods |
US20110071893A1 (en) | 2009-09-23 | 2011-03-24 | Harshita Malhotra | system and method for interactively connecting users and third party providers to individual or aggregated to-do list task items of users within the task management system |
US20110093538A1 (en) | 2009-10-15 | 2011-04-21 | International Business Machines Corporation | Collaborative calendar and workflow management |
US20110093619A1 (en) | 2009-10-16 | 2011-04-21 | Ianywhere Solutions, Inc. | Synchronizing Tasks between Mobile Devices and Servers |
US20110113365A1 (en) | 2009-11-09 | 2011-05-12 | Microsoft Corporation | Scrolling large data sets |
JP5400599B2 (en) | 2009-12-18 | 2014-01-29 | 株式会社日立製作所 | GUI customization method, system, and program |
US20110161128A1 (en) | 2009-12-31 | 2011-06-30 | Mckesson Financial Holdings Limited | Scheduling and Assigning Units of Work |
US8375034B2 (en) | 2010-01-27 | 2013-02-12 | Google Inc. | Automatically schedule and re-schedule meetings using reschedule factors for conflicting calendar events |
US8572477B1 (en) | 2010-01-29 | 2013-10-29 | Asana, Inc. | Web-based incremental computing |
US9152668B1 (en) | 2010-01-29 | 2015-10-06 | Asana, Inc. | Asynchronous computation batching |
US8627199B1 (en) | 2010-01-29 | 2014-01-07 | Asana, Inc. | Incremental computing of changes to computer user interfaces |
US9940594B1 (en) * | 2010-02-19 | 2018-04-10 | Elance, Inc. | Digital workroom |
WO2011105768A2 (en) | 2010-02-23 | 2011-09-01 | 엘지전자 주식회사 | Refrigerator including a terminal, and method for controlling same |
US9471648B2 (en) | 2010-03-01 | 2016-10-18 | Salesforce.Com, Inc. | System, method and computer program product for displaying one or more data sets to a user |
US8429521B2 (en) | 2010-04-12 | 2013-04-23 | Google Inc. | Scrolling in large hosted data set |
US20110270644A1 (en) | 2010-04-29 | 2011-11-03 | Selex Sistemi Integrati S.P.A. | System and method to estimate the effects of risks on the time progression of projects |
CA2738428A1 (en) | 2010-04-30 | 2011-10-30 | Iliv Technologies Inc. | Collaboration tool |
US20140058801A1 (en) | 2010-06-04 | 2014-02-27 | Sapience Analytics Private Limited | System And Method To Measure, Aggregate And Analyze Exact Effort And Time Productivity |
US20170116552A1 (en) | 2010-06-04 | 2017-04-27 | Sapience Analytics Private Limited | System and Method to Measure, Aggregate and Analyze Exact Effort and Time Productivity |
US8843832B2 (en) | 2010-07-23 | 2014-09-23 | Reh Hat, Inc. | Architecture, system and method for a real-time collaboration interface |
US20120030194A1 (en) | 2010-07-29 | 2012-02-02 | Research In Motion Limited | Identification and scheduling of events on a communication device |
US20120035942A1 (en) | 2010-08-06 | 2012-02-09 | Sven Graupner | Managing business relationships using a third-party service |
US20120066030A1 (en) | 2010-09-09 | 2012-03-15 | Limpert Bruce R | Performance Management System And Dashboard |
US20120072251A1 (en) | 2010-09-20 | 2012-03-22 | Cristian Mircean | Method, management procedure, process, an instrument and apparatus for delay estimation and mitigation of delay risks in projects and program |
US20120079449A1 (en) | 2010-09-29 | 2012-03-29 | General Electric Company | Systems and methods for facilitating visual management of an agile development process |
US20130103412A1 (en) | 2011-03-14 | 2013-04-25 | ClearCare, Inc. | System and apparatus for generating work schedules |
US9824334B2 (en) | 2011-07-11 | 2017-11-21 | ClearCare, Inc. | System for updating a calendar or task status in home care scheduling via telephony |
EP2451141B1 (en) | 2010-11-09 | 2018-11-07 | BlackBerry Limited | Methods and apparatus to display mobile device contents |
US20120131191A1 (en) | 2010-11-19 | 2012-05-24 | Research In Motion Limited | Mobile communication device, server, and method of facilitating resource reservations |
US20120137235A1 (en) | 2010-11-29 | 2012-05-31 | Sabarish T S | Dynamic user interface generation |
US9454623B1 (en) | 2010-12-16 | 2016-09-27 | Bentley Systems, Incorporated | Social computer-aided engineering design projects |
US8463902B2 (en) | 2010-12-17 | 2013-06-11 | Verizon Patent And Licensing Inc. | Work unit adapter for content processing with third party network elements |
US9201952B1 (en) | 2010-12-21 | 2015-12-01 | Google Inc. | User interface for activity status and history |
EP2659363A4 (en) | 2010-12-30 | 2016-06-29 | Kyle Kleinbart | System and method for online communications management |
WO2012099617A1 (en) | 2011-01-20 | 2012-07-26 | Box.Net, Inc. | Real time notification of activities that occur in a web-based collaboration environment |
US9311629B2 (en) | 2011-02-15 | 2016-04-12 | Bank Of America Corporation | Information management problem initiative system |
US9165289B2 (en) | 2011-02-28 | 2015-10-20 | Ricoh Company, Ltd. | Electronic meeting management for mobile wireless devices with post meeting processing |
US8554832B1 (en) | 2011-03-01 | 2013-10-08 | Asana, Inc. | Server side user interface simulation |
US9659260B2 (en) | 2011-03-15 | 2017-05-23 | Dan Caligor | Calendar based task and time management systems and methods |
US9383917B2 (en) | 2011-03-28 | 2016-07-05 | Microsoft Technology Licensing, Llc | Predictive tiling |
WO2012131962A1 (en) | 2011-03-30 | 2012-10-04 | 富士通株式会社 | Task execution control device, task execution control system, and task execution control method |
US8732151B2 (en) | 2011-04-01 | 2014-05-20 | Microsoft Corporation | Enhanced query rewriting through statistical machine translation |
US9558013B2 (en) | 2011-04-12 | 2017-01-31 | Citrix Systems, Inc. | Responsive scroller controls in server-hosted applications |
JP5787606B2 (en) | 2011-05-02 | 2015-09-30 | キヤノン株式会社 | Information processing apparatus, information processing method, and program |
US20120296982A1 (en) | 2011-05-17 | 2012-11-22 | International Business Machines Corporation | Automatic Scheduling Tool |
US8683473B2 (en) | 2011-05-27 | 2014-03-25 | International Business Machines Corporation | Dynamic task association between independent, unrelated projects |
US8954431B2 (en) | 2011-06-09 | 2015-02-10 | Xerox Corporation | Smart collaborative brainstorming tool |
US8601198B2 (en) | 2011-06-30 | 2013-12-03 | Intel Corporation | Controllable transaction synchronization for merging peripheral devices |
GB2503625A (en) | 2011-07-08 | 2014-01-01 | Box Inc | Collaboration sessions in a workspace on cloud-based content management system |
US9652741B2 (en) | 2011-07-08 | 2017-05-16 | Box, Inc. | Desktop application for access and interaction with workspaces in a cloud-based content management system and synchronization mechanisms thereof |
US9009096B2 (en) | 2011-07-12 | 2015-04-14 | Ebay Inc. | Recommendations in a computing advice facility |
US9179035B2 (en) | 2011-07-19 | 2015-11-03 | Samsung Electronics Co., Ltd. | Method of editing static digital combined images comprising images of multiple objects |
EP2560134A1 (en) | 2011-08-19 | 2013-02-20 | Agor Services BVBA | A platform and method enabling collaboration between value chain partners |
US8384726B1 (en) | 2011-08-31 | 2013-02-26 | Google Inc. | Selective rendering of off-screen content |
US9195968B2 (en) | 2011-09-09 | 2015-11-24 | Microsoft Technology Licensing, Llc | Cloud-based broker service for digital assistants |
US20130066944A1 (en) | 2011-09-13 | 2013-03-14 | International Business Machines Corporation | Social gathering of distributed knowledge |
WO2013059924A1 (en) | 2011-10-26 | 2013-05-02 | Godwin Liu | System and method for managing project, process, and meeting tasks over a network |
US20140200944A1 (en) | 2011-11-08 | 2014-07-17 | Matchware A/S | Automation of meeting scheduling and task list access permissions within a meeting series |
US8990307B2 (en) | 2011-11-16 | 2015-03-24 | Box, Inc. | Resource effective incremental updating of a remote client with events which occurred via a cloud-enabled platform |
US20170323350A1 (en) | 2011-11-17 | 2017-11-09 | Tonya Laderer | Cloud-based workflow management platform defined by permission-based roles and relationships for administering, creating, and processing commercial advertising work orders |
US20130151421A1 (en) | 2011-12-08 | 2013-06-13 | Oracle International Corporation | Real-time project progress entry: applying project team member-entered progress immediately to the project plan |
US8868655B2 (en) | 2011-12-09 | 2014-10-21 | Kabam, Inc. | User affiliations spanning multiple virtual spaces |
US20130173486A1 (en) | 2011-12-29 | 2013-07-04 | Sap Ag | Collaboration cloud |
US9904435B2 (en) | 2012-01-06 | 2018-02-27 | Box, Inc. | System and method for actionable event generation for task delegation and management via a discussion forum in a web-based collaboration environment |
US20130179208A1 (en) | 2012-01-11 | 2013-07-11 | Microsoft Corporation | Workflow tasks |
US9965745B2 (en) | 2012-02-24 | 2018-05-08 | Box, Inc. | System and method for promoting enterprise adoption of a web-based collaboration environment |
US20130246110A1 (en) | 2012-03-15 | 2013-09-19 | Microsoft Corporation | Visualizing resource requirements along a timeline |
CN104380222B (en) | 2012-03-28 | 2018-03-27 | 泰瑞·克劳福德 | Sector type is provided and browses the method and system for having recorded dialogue |
US9024752B2 (en) | 2012-04-05 | 2015-05-05 | Amadeus S.A.S. | Traveler hurry status monitor |
US20130275229A1 (en) | 2012-04-16 | 2013-10-17 | Madhav Moganti | Apparatus and method for universal personal data portability |
US8699691B2 (en) | 2012-04-18 | 2014-04-15 | Avaya Inc. | Multi-tasking relief |
US8768751B2 (en) | 2012-04-25 | 2014-07-01 | Sap Ag | Enterprise gamification system for awarding employee performance |
US20130317871A1 (en) | 2012-05-02 | 2013-11-28 | MobileWorks, Inc. | Methods and apparatus for online sourcing |
US9990636B1 (en) | 2012-05-24 | 2018-06-05 | Jpmorgan Chase Bank, N.A. | Enterprise fulfillment system with dynamic prefetching, secured data access, system monitoring, and performance optimization capabilities |
US20130321467A1 (en) | 2012-06-01 | 2013-12-05 | Microsoft Corporation | Using snapshots to represent slow applications |
US9251484B2 (en) | 2012-06-01 | 2016-02-02 | International Business Machines Corporation | Predicting likelihood of on-time product delivery, diagnosing issues that threaten delivery, and exploration of likely outcome of different solutions |
US20130339099A1 (en) | 2012-06-15 | 2013-12-19 | Daood Aidroos | Method and system for business program and service planning, delivery and management |
US20130339831A1 (en) | 2012-06-15 | 2013-12-19 | Microsoft Corporation | Dynamic reports connected to project data |
EP2865202B1 (en) | 2012-06-22 | 2017-04-12 | Google, Inc. | Presenting information for a current location or time |
US20140007005A1 (en) | 2012-06-29 | 2014-01-02 | Evernote Corporation | Scrollable calendar with combined date and time controls |
US20140012603A1 (en) | 2012-07-09 | 2014-01-09 | James Scanlon | Capacity planning and modeling for optimization of task outcomes |
US9268875B2 (en) | 2012-07-13 | 2016-02-23 | Microsoft Technology Licensing, Llc | Extensible content focus mode |
US8863021B1 (en) | 2012-07-26 | 2014-10-14 | Google Inc. | Scheduling calendar events for tasks |
US20140036639A1 (en) | 2012-08-02 | 2014-02-06 | Cozi Group Inc. | Family calendar |
US20140040780A1 (en) | 2012-08-06 | 2014-02-06 | Punch Technologies, Inc. | System and method for providing collaboration information around projects and activities using remote time triggers |
US20140156539A1 (en) | 2012-08-17 | 2014-06-05 | CrowdCare Corporation | Device Profile-Based Rule Making for Customer Care |
US8800422B2 (en) | 2012-08-20 | 2014-08-12 | Ra Brands, L.L.C. | Bolt assembly for firearms |
JP2015531505A (en) | 2012-09-10 | 2015-11-02 | プライベート セクレタリー リミテッド | Conference coordination system and method |
US9361594B2 (en) | 2012-09-24 | 2016-06-07 | Sap Se | Generating time slot for managing time across multiple time zones |
US9959420B2 (en) | 2012-10-02 | 2018-05-01 | Box, Inc. | System and method for enhanced security and management mechanisms for enterprise administrators in a cloud-based environment |
US20140101310A1 (en) | 2012-10-04 | 2014-04-10 | Box, Inc. | Seamless access, editing, and creation of files in a web interface or mobile interface to a collaborative cloud platform |
US20140236663A1 (en) | 2012-11-13 | 2014-08-21 | Terry Smith | System and method for providing unified workflows integrating multiple computer network resources |
US9575998B2 (en) | 2012-12-12 | 2017-02-21 | Adobe Systems Incorporated | Adaptive presentation of content based on user action |
US20140172478A1 (en) | 2012-12-13 | 2014-06-19 | TCT Hungqary Kft. | Methods and system for automatic work logging and tracking |
US9514448B2 (en) | 2012-12-28 | 2016-12-06 | Intel Corporation | Comprehensive task management |
US10579228B2 (en) | 2013-01-11 | 2020-03-03 | Synacor, Inc. | Method and system for configuring selection of contextual dashboards |
US8639552B1 (en) | 2013-01-24 | 2014-01-28 | Broadvision, Inc. | Systems and methods for creating and sharing tasks |
US9111091B2 (en) | 2013-01-29 | 2015-08-18 | International Business Machines Corporation | Automatic extraction, modeling, and code mapping of application user interface display screens and components |
US9900396B2 (en) | 2013-02-14 | 2018-02-20 | Comcast Cable Communications, Llc | Predictive content caching |
US9002763B2 (en) | 2013-02-14 | 2015-04-07 | International Business Machines Corporation | Work-item notification classifier |
US20140244334A1 (en) | 2013-02-26 | 2014-08-28 | Oracle International Corporation | Facilitating allocation of resources to tasks |
US9405532B1 (en) | 2013-03-06 | 2016-08-02 | NetSuite Inc. | Integrated cloud platform translation system |
US20140257892A1 (en) | 2013-03-07 | 2014-09-11 | International Business Machines Corporation | Social project collaboration through self-organizing teams |
US9426216B2 (en) | 2013-03-10 | 2016-08-23 | Dropbox, Inc. | Content item sharing and synchronization system with team shared folders |
US9600136B1 (en) | 2013-03-11 | 2017-03-21 | Workday, Inc. | Data object extensibility |
US20140279294A1 (en) | 2013-03-14 | 2014-09-18 | Nordstrom, Inc. | System and methods for order fulfillment, inventory management, and providing personalized services to customers |
US20140310050A1 (en) | 2013-04-12 | 2014-10-16 | International Business Machines Corporation | Methods And Apparatus For Project Portfolio Management |
US20140310047A1 (en) | 2013-04-12 | 2014-10-16 | Oracle International Corporation | Simplifying scheduling of dependent tasks in a collaborative project management environment |
US9830398B2 (en) | 2013-04-17 | 2017-11-28 | Salesforce.Com, Inc. | System and method for associating dynamic objects with database records |
CN105247548B (en) | 2013-05-21 | 2019-09-10 | 思杰系统有限公司 | User in collaboration workspace system based on application defines workflow |
JP6092718B2 (en) | 2013-06-11 | 2017-03-08 | 株式会社日立製作所 | Operation planning support system and method |
US9304648B2 (en) | 2013-06-26 | 2016-04-05 | Google Inc. | Video segments for a video related to a task |
US9772754B2 (en) | 2013-06-27 | 2017-09-26 | Progressly, Inc. | Collaborative network-based graphical progress management tool |
JP2015014939A (en) | 2013-07-05 | 2015-01-22 | 富士通株式会社 | Work management method and work management program |
US20150058053A1 (en) | 2013-08-20 | 2015-02-26 | Oracle International Corporation | Shifting a group of tasks along a timeline |
US9367117B2 (en) | 2013-08-29 | 2016-06-14 | Sony Interactive Entertainment America Llc | Attention-based rendering and fidelity |
US10509527B2 (en) | 2013-09-13 | 2019-12-17 | Box, Inc. | Systems and methods for configuring event-based automation in cloud-based collaboration platforms |
WO2015036817A1 (en) | 2013-09-15 | 2015-03-19 | Yogesh Chunilal Rathod | Structured updated status, requests, user data & programming based presenting & accessing of connections |
US9298506B2 (en) | 2013-09-30 | 2016-03-29 | Teradata Us, Inc. | Assigning resources among multiple task groups in a database system |
US20150134393A1 (en) | 2013-11-14 | 2015-05-14 | Oracle International Corporation | Enhanced control to users in placement of tasks along a timeline |
US20150188862A1 (en) | 2013-12-27 | 2015-07-02 | Entefy Inc. | Apparatus and Method for Multi-Format Communication Composition |
US9606977B2 (en) | 2014-01-22 | 2017-03-28 | Google Inc. | Identifying tasks in messages |
US20150213410A1 (en) | 2014-01-24 | 2015-07-30 | T Minus 5 Llc | Meeting Management |
US20170098197A1 (en) | 2014-02-21 | 2017-04-06 | Rna Labs Inc. | Systems and Methods for Automatically Collecting User Data and Making a Real-World Action for a User |
US20150262111A1 (en) | 2014-03-12 | 2015-09-17 | Nanyang Technological University | Apparatus and method for efficient task allocation in crowdsourcing |
US9344573B2 (en) | 2014-03-14 | 2016-05-17 | Twilio, Inc. | System and method for a work distribution service |
US9928241B2 (en) | 2014-03-18 | 2018-03-27 | Smartsheet Inc. | Systems and methods for analyzing electronic communications to dynamically improve efficiency and visualization of collaborative work environments |
US20160342927A1 (en) | 2014-03-28 | 2016-11-24 | Hewlett Packard Enterprise Development Lp | Systems and methods for providing an information technology interface |
US10091287B2 (en) | 2014-04-08 | 2018-10-02 | Dropbox, Inc. | Determining presence in an application accessing shared and synchronized content |
US20150312375A1 (en) | 2014-04-25 | 2015-10-29 | Microsoft Corporation | Pre-fetching grid blocks by user intent |
US9418348B2 (en) | 2014-05-05 | 2016-08-16 | Oracle International Corporation | Automatic task assignment system |
US20150339006A1 (en) | 2014-05-21 | 2015-11-26 | Facebook, Inc. | Asynchronous Preparation of Displayable Sections of a Graphical User Interface |
WO2015183247A1 (en) | 2014-05-28 | 2015-12-03 | Hitachi Data Systems Corporation | System and method of collision management in a namespace of a storage system |
US20150348496A1 (en) | 2014-05-30 | 2015-12-03 | Pixtronix, Inc. | Systems and methods for selecting display operation modes |
US20150363092A1 (en) | 2014-05-30 | 2015-12-17 | Contatta, Inc. | Systems and methods for collaborative electronic communications |
US10062045B2 (en) * | 2014-06-12 | 2018-08-28 | International Business Machines Corporation | Project workspace prioritization |
WO2015200681A1 (en) | 2014-06-25 | 2015-12-30 | James Noland | Method, system, and medium for workflow management of document processing |
US10192181B2 (en) | 2014-06-26 | 2019-01-29 | Oracle International Corporation | Resource demand-based project team staffing |
US20160012368A1 (en) | 2014-07-14 | 2016-01-14 | Rocket Lawyer Incorporated | Real-Time User Interface for Prioritized Professional Work Queue |
US20180260081A1 (en) * | 2014-07-30 | 2018-09-13 | Google Inc. | Task switching or task launching based on a ranked list of tasks |
US20160048408A1 (en) | 2014-08-13 | 2016-02-18 | OneCloud Labs, Inc. | Replication of virtualized infrastructure within distributed computing environments |
JP6025154B2 (en) | 2014-08-14 | 2016-11-16 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | System, method and program for managing a project |
US20160063449A1 (en) | 2014-08-28 | 2016-03-03 | Fmr Llc | Method and system for scheduling a meeting |
US10217528B2 (en) | 2014-08-29 | 2019-02-26 | General Electric Company | Optimizing state transition set points for schedule risk management |
US9894119B2 (en) | 2014-08-29 | 2018-02-13 | Box, Inc. | Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms |
US10063507B2 (en) | 2014-09-08 | 2018-08-28 | Accenture Global Services Limited | Digital collaboration process enablement tool |
US20160110670A1 (en) | 2014-10-20 | 2016-04-21 | Sap Se | Relational analysis of business objects |
US9720737B2 (en) | 2014-10-31 | 2017-08-01 | Microsoft Technology Licensing, Llc | Controlling resource allocation with automated consumption against a work breakdown structure |
US20160140501A1 (en) | 2014-11-17 | 2016-05-19 | Oleg Figlin | Collaborative project execution in the cloud |
US20160140474A1 (en) | 2014-11-18 | 2016-05-19 | Tenore Ltd. | System and method for automated project performance analysis and project success rate prediction |
US10810222B2 (en) | 2014-11-24 | 2020-10-20 | Asana, Inc. | Continuously scrollable calendar user interface |
US10007406B1 (en) | 2014-11-24 | 2018-06-26 | Evernote Corporation | Adaptive writing interface |
US20160148157A1 (en) | 2014-11-25 | 2016-05-26 | Sanju Walia | Managing activities in an organization |
US20160180277A1 (en) | 2014-12-17 | 2016-06-23 | Avaya Inc. | Automated responses to projected contact center agent fatigue and burnout |
US20160182311A1 (en) | 2014-12-19 | 2016-06-23 | Tagatoo, Inc. | Method, systems, media, and platforms for improved workflow management |
US20160180298A1 (en) | 2014-12-19 | 2016-06-23 | Greg McClement | Task map visualization |
CA2974568A1 (en) | 2015-01-21 | 2016-07-28 | Solufy Information Technologies Inc. | Project and resource planning methods and systems |
US20160224939A1 (en) | 2015-02-04 | 2016-08-04 | Broadvision, Inc. | Systems and methods for managing tasks |
EP3064602A1 (en) | 2015-03-05 | 2016-09-07 | Heraeus Deutschland GmbH & Co. KG | Method for the production of elemental rhodium |
US10373084B2 (en) | 2015-03-18 | 2019-08-06 | Adp, Llc | Integrated resource tracking system |
US10496943B2 (en) | 2015-03-30 | 2019-12-03 | Oracle International Corporation | Visual task assignment system |
US10001911B2 (en) | 2015-04-10 | 2018-06-19 | International Business Machines Corporation | Establishing a communication link between plural participants based on preferences |
US11057388B2 (en) | 2015-05-08 | 2021-07-06 | Craig Technical Consulting, Inc. | Method and computer program product for creating enterprise management systems |
US10083412B2 (en) | 2015-05-14 | 2018-09-25 | Atlassian Pty Ltd | Systems and methods for scheduling work items |
US9882976B1 (en) | 2015-06-16 | 2018-01-30 | Amazon Technologies, Inc. | Supporting heterogeneous environments during code deployment |
US9674361B2 (en) | 2015-06-29 | 2017-06-06 | Genesys Telecommunications Laboratories, Inc. | System and method for intelligent task management in a workbin |
US9904714B2 (en) | 2015-06-30 | 2018-02-27 | International Business Machines Corporation | Crowd sourcing of device sensor data for real time response |
CN106337237B (en) | 2015-07-07 | 2020-02-18 | 恩智浦美国有限公司 | Woven signal routing substrate for wearable electronic devices |
CN105072018A (en) | 2015-07-10 | 2015-11-18 | 阿里巴巴集团控股有限公司 | Working state prompt method and device |
US10261669B2 (en) | 2015-07-14 | 2019-04-16 | Adobe Inc. | Publishing electronic documents utilizing navigation information |
JP2017027116A (en) | 2015-07-16 | 2017-02-02 | 富士ゼロックス株式会社 | Process control device and process control program |
CA2937092A1 (en) | 2015-08-05 | 2017-02-05 | Wal-Mart Stores, Inc. | Productivity evaluation systems and methods |
US10308992B2 (en) | 2015-08-20 | 2019-06-04 | Ford Motor Company | Method and system for selectively softening hot stamped parts by induction heating |
US20210110347A1 (en) | 2015-08-22 | 2021-04-15 | Salim B. KHALIL | Automated, integrated and complete computer program/project management solutions standardizes and optimizes management processes and procedures utilizing customizable and flexible systems and methods |
US20170061341A1 (en) | 2015-09-01 | 2017-03-02 | Go Daddy Operating Company, LLC | Workflow management for crowd worker tasks with fixed throughput and budgets |
JP6354715B2 (en) * | 2015-09-08 | 2018-07-11 | カシオ計算機株式会社 | Work support system, work support method and program |
CA2916503C (en) | 2015-09-09 | 2023-06-13 | Patrick Edward Norton | Work project systems and methods |
US10320797B2 (en) | 2015-09-25 | 2019-06-11 | International Business Machines Corporation | Enabling a multi-dimensional collaborative effort system |
GB201517437D0 (en) | 2015-10-02 | 2015-11-18 | Pekama Ltd | An access control system and method |
US11775937B2 (en) | 2015-10-08 | 2023-10-03 | Arris Enterprises Llc | Dynamic capacity ranges for workforce routing |
US10496940B2 (en) | 2015-12-01 | 2019-12-03 | Sap Se | Presenting resource utilization in a user interface |
US10437828B2 (en) | 2015-12-18 | 2019-10-08 | Sap Se | Controlled reference process extensibility framework |
US20170192642A1 (en) | 2015-12-31 | 2017-07-06 | Opentv, Inc. | Systems and methods for enabling transitions between items of content based on swipe gestures |
US10074066B2 (en) | 2016-01-16 | 2018-09-11 | International Business Machines Corporation | Two phase predictive approach for supply network optimization |
JP6675229B2 (en) | 2016-02-29 | 2020-04-01 | 東芝テック株式会社 | Work assignment support device, terminal device, and program |
US20170255455A1 (en) | 2016-03-03 | 2017-09-07 | International Business Machines Corporation | Automated customization of software feature availability based on usage patterns and history |
US9814420B2 (en) | 2016-03-09 | 2017-11-14 | International Business Machines Corporation | Burnout symptoms detection and prediction |
US20170316367A1 (en) | 2016-04-29 | 2017-11-02 | Progressly, Inc. | Collaborative Network-Based Graphical Progress Management Platform for Integration with a Collaborative Software Tool |
US20170317898A1 (en) | 2016-04-29 | 2017-11-02 | Progressly, Inc. | Collaborative Network-Based Graphical Progress Management Platform for Providing Data Monitoring and Data Analysis of Third Party Services |
KR101760051B1 (en) | 2016-05-04 | 2017-07-24 | 엔에이치엔엔터테인먼트 주식회사 | System and method for providing a work allocation, and collaborative |
US10733556B2 (en) | 2016-05-09 | 2020-08-04 | Mighty AI LLC | Automated tasking and accuracy assessment systems and methods for assigning and assessing individuals and tasks |
US10346635B2 (en) | 2016-05-31 | 2019-07-09 | Genesys Telecommunications Laboratories, Inc. | System and method for data management and task routing based on data tagging |
US11789579B2 (en) | 2016-06-01 | 2023-10-17 | Meta Platforms, Inc. | Methods and systems for distinguishing messages in a group conversation |
US10706484B1 (en) | 2016-06-15 | 2020-07-07 | Resource Environmental Solutions, LLC | Methods, systems, and computer readable media for combining pollution source information with geographic and/or temporal information for a land disturbing construction site |
US10382501B2 (en) | 2016-06-29 | 2019-08-13 | Ricoh Company, Ltd. | Multifunction collaboration within an electronic meeting |
US20180032524A1 (en) | 2016-07-29 | 2018-02-01 | International Business Machines Corporation | Document Recommendation Method Based on Skill |
US10671692B2 (en) | 2016-08-12 | 2020-06-02 | Adobe Inc. | Uniquely identifying and tracking selectable web page objects |
US20180052943A1 (en) | 2016-08-18 | 2018-02-22 | Qualcomm Incorporated | Systems and methods for controlling webpage pre-rendering |
US10387811B2 (en) | 2016-08-29 | 2019-08-20 | International Business Machines Corporation | Optimally rearranging team members in an agile environment |
US10560417B2 (en) | 2016-08-31 | 2020-02-11 | Yva.Ai, Inc. | Task assistant |
JP6870242B2 (en) | 2016-08-31 | 2021-05-12 | 株式会社リコー | Conference support system, conference support device, and conference support method |
US10332073B2 (en) | 2016-09-08 | 2019-06-25 | International Business Machines Corporation | Agile team structure and processes recommendation |
US10733553B2 (en) | 2016-09-15 | 2020-08-04 | Microsoft Technology Licensing, Llc | Action item extraction for work item creation |
US20180088754A1 (en) | 2016-09-29 | 2018-03-29 | Moovila, LLC | Electronic ecosystem platform |
US20180095938A1 (en) | 2016-09-30 | 2018-04-05 | Sap Se | Synchronized calendar and timeline adaptive user interface |
US10361975B2 (en) | 2016-10-10 | 2019-07-23 | Microsoft Technology Licensing, Llc | Messaging bot selection in multi-bot chat sessions |
US10235156B2 (en) | 2016-12-01 | 2019-03-19 | Entit Software Llc | Versioned extension points of graphical user interfaces |
US10460277B2 (en) | 2016-12-14 | 2019-10-29 | Business Objects Software Limited | Business intelligence language macros |
WO2018109589A1 (en) | 2016-12-15 | 2018-06-21 | Walkme Ltd. | Updating data records by adding editing functions to non-editable display elements |
US10796255B2 (en) | 2016-12-29 | 2020-10-06 | Dropbox, Inc. | Managing project tasks using content items |
US10614419B2 (en) | 2016-12-30 | 2020-04-07 | Dropbox, Inc. | Managing tasks in a content management system |
US10803541B2 (en) | 2017-02-03 | 2020-10-13 | Jasci LLC | Systems and methods for warehouse management |
US20180247352A1 (en) | 2017-02-27 | 2018-08-30 | Ncr Corporation | Chatbot order submission |
JP6859795B2 (en) | 2017-03-28 | 2021-04-14 | 富士通株式会社 | Relay communication method, relay communication program, and relay communication device |
CN106970992A (en) | 2017-03-31 | 2017-07-21 | 上海小蚁科技有限公司 | A kind of page cache method and device |
US10423443B2 (en) | 2017-04-03 | 2019-09-24 | Oracle International Corporation | Task management interface |
US20180316636A1 (en) | 2017-04-28 | 2018-11-01 | Hrb Innovations, Inc. | Context-aware conversational assistant |
US20180331842A1 (en) | 2017-05-15 | 2018-11-15 | Microsoft Technology Licensing, Llc | Generating a transcript to capture activity of a conference session |
US11194551B2 (en) | 2017-06-07 | 2021-12-07 | Ab Initio Technology Llc | Dataflow graph configuration |
US10404636B2 (en) | 2017-06-15 | 2019-09-03 | Google Llc | Embedded programs and interfaces for chat conversations |
US10498675B2 (en) | 2017-06-15 | 2019-12-03 | GM Global Technology Operations LLC | Enhanced electronic chat efficiency |
CN107273031B (en) | 2017-06-23 | 2020-10-16 | 阿里巴巴(中国)有限公司 | Information flow page loading method and device |
US20190005048A1 (en) | 2017-06-29 | 2019-01-03 | Uber Technologies, Inc. | Optimizing media presentation within an application |
CN109240677B (en) | 2017-07-07 | 2020-10-16 | 阿里巴巴集团控股有限公司 | Layer processing method and device |
US20190014070A1 (en) | 2017-07-10 | 2019-01-10 | Findo, Inc. | Personal automated task assistant |
US10977434B2 (en) | 2017-07-11 | 2021-04-13 | Asana, Inc. | Database model which provides management of custom fields and methods and apparatus therfor |
US10423307B2 (en) | 2017-07-12 | 2019-09-24 | The Toronto-Dominion Bank | System and method for indicating data transfer method selection |
US11079899B2 (en) | 2017-07-26 | 2021-08-03 | Microsoft Technology Licensing, Llc | Dynamic eye-gaze dwell times |
US11700137B2 (en) | 2017-08-26 | 2023-07-11 | Vmware, Inc. | Collaborative access to virtual desktops |
US20190080289A1 (en) | 2017-09-08 | 2019-03-14 | Gliffy, Inc. | Graphical project management tool |
US10867128B2 (en) | 2017-09-12 | 2020-12-15 | Microsoft Technology Licensing, Llc | Intelligently updating a collaboration site or template |
US11531940B2 (en) | 2017-09-27 | 2022-12-20 | Microsoft Technology Licensing, Llc | Implicit status tracking of tasks and management of task reminders based on device signals |
JP6847801B2 (en) | 2017-09-28 | 2021-03-24 | 株式会社日立製作所 | Design support device and design support method |
US11720813B2 (en) | 2017-09-29 | 2023-08-08 | Oracle International Corporation | Machine learning platform for dynamic model selection |
US10296577B1 (en) | 2017-11-03 | 2019-05-21 | Dropbox, Inc. | Spreadsheet comment navigation |
US10282405B1 (en) | 2017-11-03 | 2019-05-07 | Dropbox, Inc. | Task management in a collaborative spreadsheet environment |
US20190138961A1 (en) | 2017-11-07 | 2019-05-09 | Indidesk, S.L. (fna Smart Canvas Solutions Espana, S.L.) | System and method for project management using artificial intelligence |
US10380558B2 (en) | 2017-11-08 | 2019-08-13 | International Business Machines Corporation | Intelligent self-service delivery advisor |
US11182706B2 (en) | 2017-11-13 | 2021-11-23 | International Business Machines Corporation | Providing suitable strategies to resolve work items to participants of collaboration system |
US11140174B2 (en) | 2017-12-13 | 2021-10-05 | Jpmorgan Chase Bank, N.A. | Time and location controlled centralized access management system |
US10831486B2 (en) | 2017-12-14 | 2020-11-10 | Adobe Inc. | Automation of sequences of actions |
WO2019139778A2 (en) | 2018-01-10 | 2019-07-18 | Walmart Apollo, Llc | System for relational-impact based task management |
US10623359B1 (en) | 2018-02-28 | 2020-04-14 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US11138021B1 (en) | 2018-04-02 | 2021-10-05 | Asana, Inc. | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US10613735B1 (en) | 2018-04-04 | 2020-04-07 | Asana, Inc. | Systems and methods for preloading an amount of content based on user scrolling |
US10824995B2 (en) | 2018-05-03 | 2020-11-03 | International Business Machines Corporation | Communication enrichment recommendation |
US11074284B2 (en) | 2018-05-07 | 2021-07-27 | International Business Machines Corporation | Cognitive summarization and retrieval of archived communications |
US10796259B2 (en) | 2018-05-08 | 2020-10-06 | Microsoft Technology Licensing, Llc | Risk and dependency tracking and control system |
US20190370320A1 (en) | 2018-06-05 | 2019-12-05 | Bank Of America Corporation | System and method for provisioning multiple forms in an interface |
US10785046B1 (en) | 2018-06-08 | 2020-09-22 | Asana, Inc. | Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users |
US20210264372A1 (en) | 2018-07-04 | 2021-08-26 | Imi Material Handling Logistics Inc. | Automated human resources management and engagement system and method |
US20200019907A1 (en) | 2018-07-13 | 2020-01-16 | One Network Enterprises, Inc. | System and computer program for multi-party project schedule collaboration, synchronization and execution |
US20200059539A1 (en) | 2018-08-20 | 2020-02-20 | Landmark Graphics Corporation | Cloud-native reservoir simulation |
US10891571B2 (en) | 2018-08-23 | 2021-01-12 | Capital One Services, Llc | Task management platform |
US10846105B2 (en) | 2018-09-29 | 2020-11-24 | ILAN Yehuda Granot | User interface advisor |
US10616151B1 (en) | 2018-10-17 | 2020-04-07 | Asana, Inc. | Systems and methods for generating and presenting graphical user interfaces |
US11153152B2 (en) | 2018-11-21 | 2021-10-19 | Cisco Technology, Inc. | System and methods to validate issue detection and classification in a network assurance system |
US10956845B1 (en) | 2018-12-06 | 2021-03-23 | Asana, Inc. | Systems and methods for generating prioritization models and predicting workflow prioritizations |
US11113667B1 (en) | 2018-12-18 | 2021-09-07 | Asana, Inc. | Systems and methods for providing a dashboard for a collaboration work management platform |
US10684870B1 (en) | 2019-01-08 | 2020-06-16 | Asana, Inc. | Systems and methods for determining and presenting a graphical user interface including template metrics |
US11204683B1 (en) | 2019-01-09 | 2021-12-21 | Asana, Inc. | Systems and methods for generating and tracking hardcoded communications in a collaboration management platform |
EP3686748B1 (en) | 2019-01-22 | 2022-05-04 | PRMA Consulting Limited | Synchronizing content blocks between multiple electronic documents |
WO2020223247A1 (en) | 2019-04-29 | 2020-11-05 | Jpmorgan Chase Bank, N.A. | Systems and methods for data-driven infrastructure controls |
US11588764B2 (en) | 2019-10-30 | 2023-02-21 | Amazon Technologies, Inc. | Extensible framework for constructing autonomous workflows |
US11341445B1 (en) | 2019-11-14 | 2022-05-24 | Asana, Inc. | Systems and methods to measure and visualize threshold of user workload |
US11302284B2 (en) | 2020-01-17 | 2022-04-12 | Microsoft Technology Licensing, Llc | Focus assist mode for user interfaces |
US11095468B1 (en) | 2020-02-13 | 2021-08-17 | Amazon Technologies, Inc. | Meeting summary service |
US11568339B2 (en) | 2020-08-18 | 2023-01-31 | Asana, Inc. | Systems and methods to characterize units of work based on business objectives |
-
2018
- 2018-04-02 US US15/908,670 patent/US11138021B1/en active Active
-
2021
- 2021-08-20 US US17/408,030 patent/US11720378B2/en active Active
-
2023
- 2023-04-21 US US18/305,100 patent/US20230251880A1/en active Pending
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11831457B2 (en) | 2018-06-08 | 2023-11-28 | Asana, Inc. | Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users |
Also Published As
Publication number | Publication date |
---|---|
US11138021B1 (en) | 2021-10-05 |
US20210382734A1 (en) | 2021-12-09 |
US11720378B2 (en) | 2023-08-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11720378B2 (en) | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform | |
US11943179B2 (en) | Systems and methods for generating and presenting graphical user interfaces | |
US11956193B2 (en) | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment | |
US11561677B2 (en) | Systems and methods for generating and tracking hardcoded communications in a collaboration management platform | |
US11810074B2 (en) | Systems and methods for providing a dashboard for a collaboration work management platform | |
US11537564B2 (en) | Group-based communication interface with subsidiary file communications | |
US9253130B2 (en) | Systems and methods for supporting social productivity using a dashboard | |
JP7079397B2 (en) | Systems and methods for initiating processing actions using auto-generated data from group-based communication systems | |
US20170061389A1 (en) | Efficiency of scheduling of a meeting time | |
US11902344B2 (en) | Systems and methods to present views of records in chat sessions between users of a collaboration environment | |
US10977242B2 (en) | Systems and methods for managing designated content items | |
US20210216945A1 (en) | System for processing enterprise data to improve task planning | |
US11282036B1 (en) | Systems and methods to generate agendas for group meetings | |
US20240019993A1 (en) | Systems and methods to selectively configure features of a user interface of a computer environment to limit distractions | |
US11900323B1 (en) | Systems and methods to generate units of work within a collaboration environment based on video dictation | |
US11863601B1 (en) | Systems and methods to execute branching automation schemes in a collaboration environment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ASANA, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROSENSTEIN, JUSTIN;LU, HE;ESTRADA, ALEXANDRA;SIGNING DATES FROM 20180228 TO 20180403;REEL/FRAME:063405/0721 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |