DETAILED ACTION
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This office action is responsive to communication(s): original application filed on 10/15/2024, said application claims a priority filing date of 12/29/2021.
Claims 21-40 are pending. Claims 21, 27 and 35 are independent.
Double Patenting
The non-statutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A non-statutory obviousness-type double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on a non-statutory double patenting ground provided the conflicting application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement.
Effective January 1, 1994, a registered attorney or agent of record may sign a terminal disclaimer. A terminal disclaimer signed by the assignee must fully comply with 37 CFR 3.73(b).
Claims 21 is rejected on the ground of non-statutory obviousness-type double patenting as being unpatentable over claim 19 of US Patent 12,118,185 by Romagnoli et al. (hereinafter ‘185). Although the conflicting claims are not identical, they are not patentably distinct from each other because:
The scope of claim limitations 21 of instant application falls within the scope of the claim limitations 19 of '185 underlined below:
Instant Application 18/916346
Reference Patent # 12,118,185
Claim 21. A computer-implemented method for providing a graphical user interface of an issue tracking system, the method comprising: causing display of the graphical user interface on a display of a user device associated with a particular user account, the graphical user interface including a set of object cards, each object card including issue data extracted from a respective issue managed by the issue tracking system; in response to receiving a first user input at an interface element of a particular object card of the set of object cards, causing display of a comment interface for the particular object card, the comment interface including a set of user-generated comments, the set of user- generated comments associated with the respective issue; in response to receiving a second user input including user-generated text at a text input region of the comment interface, causing the user-generated text to be saved at the issue tracking system as a comment associated with both of the particular user account and the respective issue.
Claim 19. A computer-implemented method of providing a graphical user interface of an issue tracking system, the method comprising: receiving a request from a user device to display the graphical user interface of the issue tracking system; causing display of a set of object cards to be displayed in the graphical user interface on the user device, each object card of the set of object cards corresponding to a respective issue managed by the issue tracking system, each object card including issue data for a respective issue managed by the issue tracking system; causing display of at least one direct action control on an object card of the set of object cards; in response to a user selection of a particular direct action control of the at least one direct action control for a particular object card of the set of object cards: obtaining user permissions data for a user account associated with the user device; and in accordance with the permissions data of the user account satisfying a permissions criteria with respect to an action associated with the particular direct action control, causing the action to be performed with respect to a particular issue associated with the particular object card, wherein: the action to be performed includes adding a comment to the particular object card; and in accordance with the permissions data of the user account satisfying a permissions criteria, causing display of a popup window having a comment area, wherein subsequent to the permissions data of the user account satisfying the permissions criteria and inputting the comment in the popup window, updating display of the particular object card, the updated display comprising text of the comment.
Claims 27 and 35 are rejected on the ground of non-statutory obviousness-type double patenting as being unpatentable over claim 9 and 20 respectively of US Patent 11,556,225 by Romagnoli et al. (hereinafter ‘225). Although the conflicting claims are not identical, they are not patentably distinct from each other because:
The scope of claim limitations 27 and 35 of instant application falls within the scope of the claim limitations 9 and 20 of '225 underlined below:
Instant Application 18/916346
Reference Patent # 11,556,225
Claim 27. A computer-implemented method for providing a graphical user interface of an issue tracking system, the method comprising: causing display of the graphical user interface on a display of a user device associated with a particular user account, the graphical user interface including a set of object cards, each object card including issue data extracted from a respective issue managed by the issue tracking system; in response to a user input received at a snooze control element of a particular object card of the set of object cards, the particular object card corresponding to an open issue assigned to the particular user account, causing display of a snooze control window configured to receive user unsnooze input; in response to receiving a user unsnooze criteria via the snooze control window: causing particular the object card to be hidden from display in the graphical user interface; storing, at the issue tracking system, snooze data associated with the particular object card, the snooze data based at least in part on the user unsnooze criteria; and subsequent to a trigger condition of the snooze data being satisfied, causing the particular object card to be unhidden from display in the graphical user interface.
Claim 35. A system comprising: one or more processors; one or more non-transitory computer readable storage media storing sequences of instructions which, when executed by the one or more processors, cause the one or more processors to: receive a user request to display an activity feed interface of an issue tracking system (ITS);provide issue data and a first activity data to a user device associated with the user request; cause display, on the user device, of the activity feed interface, the activity feed interface comprising one or more issue cards, the one or more issue cards containing respective issue information extracted from the issue data; evaluate the first activity data to determine at least one issue card corresponding to an issue update received subsequent to a previous viewing of the activity feed interface; cause display, on the user device, of an activity indicator corresponding to the issue update proximate to the at least one issue card; and in response to receiving a user input via the activity indicator: obtain a second activity data; extract, from the second activity data, respective activity information corresponding to the at least one issue card; and provide at least a portion of the respective activity information to the user device, thereby causing to be displayed, on the user device, at least the portion of the respective activity information in an activity interface pane proximate to the activity indicator.
Claim 9. A method performed by a user device, the method comprising: generating a request for displaying a user interface of an issue tracking system (ITS) displaying a plurality of objects of the ITS, the request comprising an identifier of the user interface, and an identifier of the user of the user device; communicating the request to a server; receiving object data and activity data from the server in response to the user interface request, the activity data indicating new activity in one or more objects of the plurality of objects since the user last viewed the user interface; displaying the object data in a plurality of object cards; using the activity data to display activity indicators against one or more object cards corresponding to the one or more objects that have new activity; detecting selection of an interactive control to snooze an object card for a time period or until a corresponding action is performed; and generating and communicating an action message to the server, the action message comprising: the identifier of the user interface, the identifier of the user of the user device, an identifier of the object associated with the object card, and the time period or the corresponding action to be performed,
wherein each object card further comprising one or more interactive controls to: pin the object card to the user interface; hide the object card for a time period or until a corresponding action is performed; set a reminder for the object; or perform one or more actions on the object from the user interface, wherein said method further comprising: receiving a success message from the server in response to the server adding the user identifier, UI identifier, object identifier, time period or action to a snooze database; and removing the object card from the user interface.
Claim 20. A non-transitory computer readable medium comprising instructions, which when executed by a processor of a user device, cause the user device to perform operations comprising: generating a request for displaying a user interface of an issue tracking system (ITS) displaying a plurality of objects of the ITS, the request comprising an identifier of the user interface, and an identifier of the user of the user device, communicating the request to a server; receiving object data and activity data from the server in response to the user interface request, the activity data indicating new activity in one or more objects of the plurality of objects since the user last viewed the user interface; displaying the object data in a plurality of object cards; using the activity data to display one or more activity indicators against one or more object cards corresponding to the one or more objects that have new activity; detecting selection of an interactive control to snooze an object card for a time period or until a corresponding action is performed; and generating and communicating an action message to the server, the action message comprising: the identifier of the user interface, the identifier of the user of the user device, an identifier of the object associated with the object card, and the time period or the corresponding action to be performed, wherein the non-transitory computer readable medium further comprising instructions which when performed by the processor cause the user device to: generate a refresh request at a predetermined interval; communicate the refresh request to the server, the refresh request comprising at least the user identifier and the user interface identifier; receive updated activity data from the server, in response to the server determining the updated activity data for the user interface in the predetermined interval; update a local cache and display one or more additional activity indicators against one or more object cards based on the updated activity data.
In regard to dependent claims 22-26, 28-34 and 36-40, claims are rejected for fully incorporating the deficiency of their respective base claims.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Dick et al. (US Publication 2015/0205921) – Teaches snooze alert displayed in a graphical user interface.
Kennedy (US Publication 2005/0050210) – Teaches issue tracking system where issues can be filtered by any criteria.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to REZA NABI whose telephone number is (571)270-7592. The examiner can normally be reached Monday - Friday 8:00 am - 5:00 pm EST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, WILLIAM BASHORE can be reached at 571-272-4088. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/Reza Nabi/
Primary Examiner, Art Unit 2174
Prosecution Insights