Private Tasks

Private Tasks
Private Tasks is a place at the top of your My Tasks view where you can create tasks that no one else can access without your permission. It's a perfect place to enter reminders for yourself, create ad-hoc tasks that don't fit into a project, and to collaborate privately on tasks with other teammates.
You'll only see your private tasks appear at the top of the Tasks view when it's sorted by project.
If a teammate assigns a private task to you it will appear in your private tasks, but if they subscribe you to one it will not. Private tasks that you're subscribed to can be viewed in the "Subscribed" view (click Subscribed" in the sub navigation while in the Tasks tab) or by clicking the "More Tasks" dropdown in the sub-navigation, then selecting the name of the user (available only to Pro users). If you sort by project, the private tasks that you're allowed to view will appear at the top of the page.
If you create a private task but leave it unassigned, it will be viewable by any user who is subscribed to the task under Tasks>Unassigned.
To create a Private Task, type "Private Tasks" in the project field in the task pane and hit Enter or Tab down to the next field. Other teammates can still be subscribed to Private Tasks, but they will not have access to any of your other unshared private tasks.
Private tasks can also be created as quick tasks directly within the purple section of the My Tasks view. Just click into the New Task field at the bottom of this section and start creating your quick task as you usually would.
The task will appear in Private tasks once you save. You can access these tasks by clicking Tasks>My Tasks in the main and sub navigation bars. Even if you belong to more than one team, all your private tasks will be accessible from this one view.

Shortcuts to other sites to search off DuckDuckGo Learn More
This app ( Private ToDo list) which will help to you to manage and organize your life. You can: - Write and manage your tasks - Add comments and ideas for task - Set notification for task - Search...
Best way to add task to members of Microsoft Teams is with Planer app. · Open Microsoft Teams. · Select Channel you want and click on + sign. · Select Planner. · Create a new plan. · Click on + to add a new task , select a date and assign it to only person you assign to channel.
To create a Private Task , type " Private Tasks " in the project field in the task pane and hit Enter or Tab down to the next field. Other teammates can still be subscribed to Private Tasks , but they will not have access to any of your other unshared private tasks .
This is free version of organizer app " Private Tasks " which will help to you to manage and organize your life. ToDo list. You can: - Write and manage your "ToDo list" - Add comments and ideas for...
Feb 16, 2021 By " private " I mean Issues for Tasks that user wants to add for himself. Those can be related to regular work, but also can be unrelated. I.e. some form of ToDo-list. As far as I understand there are three ways to do that: 1. Set up a new Project for every User with restrictions that only User can add Issues. 2.
Dec 8, 2020 Answer: A Private Task can only be seen by the Task Creator, the Assignee, and users with the Administrator permission. Was this article helpful?
Jan 7, 2021 The newly released Personal Tasks in Teamwork lets you create and manage a private to-do list that's only visible to you and not linked to a project. Personal Tasks are designed to be added quickly and in context, so you can ease the cognitive load by getting tasks out of your head and down on paper, so to speak. Benefits of Personal Tasks :
It's not possible to create a private task within a public project, because everyone that has access to the project has access to all tasks within the project. You can, of course, always create private tasks within your My Tasks list. Read more about project permissions here. Christina_Aiko 4 September 2018 21:20 #9
To add a folder, right-click My tasks and select Create new folder. To rename or delete folders, right-click the folder and select Rename or Delete. Tasks list - Filter and display tasks based on the status you've assigned to them. Use the Filter menu to sort tasks based on different criteria.
Good Morning- I have a user who needs to report on how many PTasks there currently are in the system. I created a report with a count and added this to their dashboard.
Help your friends and family join the Duck Side!
Stay protected and informed with our privacy newsletters.
Switch to DuckDuckGo and take back your privacy!
Try our homepage that never shows these messages:
Over $3,650,000 in DuckDuckGo privacy donations.
We don't save your search history or follow you around the web.
Learn how we're dedicated to keeping you safe online.

Ask a question Get answers to your question from experts in the community
Start a discussion Share a use case, discuss your favorite features, or get input from the community
Community resources Announcements FAQ Guidelines About
Community resources Announcements FAQ Guidelines About
Community resources Announcements FAQ Guidelines About
Community Products Jira Jira Software Questions Best practice for private tasks (a user adds issues for himself not necesserely related to projects)
Best practice for private tasks (a user adds issues for himself not necesserely related to projects)

3 answers

2 accepted

Like • mogavenasan likes this
Like • Iago Docando likes this
TAGS jira-software-server server
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We're gathering information on how to use Jira Software (Data Center) for enterprise-wide deployment in mostly operational business-processes. For around 500 users.
The configuration models for key processes are already defined. Only secondary processes and non-critical requirements now left as open questions.
One of them is how to properly organize the configuration of projects, boards, issues (etc) for the ability of a every user to add "private" Issues.
By "private" I mean Issues for Tasks that user wants to add for himself. Those can be related to regular work, but also can be unrelated. I.e. some form of ToDo-list.
As far as I understand there are three ways to do that:
1. Set up a new Project for every User with restrictions that only User can add Issues.
2. Set up one Project, but with Security levels. So that any User can add Issues, but you can only watch your own Issues.
3. We are going to use a separate Project for Teams and Departments. Private tasks can be hosted in those Projects, but with more restricted Security Level, so that only Reporter could see them.
Could you please help us with advice and opinions on that matter?
Is there any other way to configure the system beside three described options?
Also if the first option is used (Individual Project for each user), would it be detrimental for the performance of the system (as there would be around 500 additional Projects)?
Jira is not really suited for this scenario. For example, if a user wants a different workflow for their own personal ToDo issues - this will add more maintenance tasks on your Jira Admins. This is just for workflow, imagine the Admin is getting requests from end-users on screens, fields, statuses, Priorities, Resolutions and etc. - this will be a pain for your Jira Admins to be handling. Plus, if you are implementing some of the niche cases on your Jira, the data would be also all over, for example, you might end up with some fields, statuses, Priorities, or Resolutions that are being used by certain small projects only.
The best application I can think of is Trello for ToDo-list - the user can customize it however they want. They have a lot of flexibility in this way.
However, if you really really want to use Jira for this scenario, then I would go for:
3. We are going to use a separate Project for Teams and Departments. Private tasks can be hosted in those Projects, but with more restricted Security Level, so that only Reporter could see them.
You can have a unique issue type, for example; "Personal" and then tie all the schemes around the Issue Type. But yea, you might get some requests to change this and that in the future which you might need to consider.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Thank you for your answer. It's on point and helpful!
Yes, it's quite apparent that Jira is not the best solution for the use-case.
But as I mentioned in the other reply, the plus side is that a user would see the full set of his tasks, not only projects and operations related ones.
And yes, for the administrators it could be additional headache. Although I think that it would be reasonable to restrict the customization of those private projects. So that a user could opt to use one, but only in a way the project is standardly configured.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Security levels won't work as you intend. They are nested (if that's the correct word).
You would have 500 security levels S1 > S2 > ... > S500 and S1 could see everything, S2 everything but S1, and so on...
Even if you set up a personal project per user, where each user is the proyect leader and only member of the project, site admins could see everything there so it would be " privacy*** ".
Jira is not meant for PERSONAL privacy, it is more centered around TEAM privacy in my opinion. And of course there's no problem having the admins seeing anything regarding any team.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

I'm not sure why are you saying that security levels won't work.
As far as my experiments go all you need is one scheme with Security Level that restricts view to (for example) Reporter, Assignee and Project lead. A user will not be able to see an Issue if he's not the Reporter / Assignee / Project lead.
Could you please elaborate a little bit on your point about the Security Levels? I'm now slightly worried that I might miss some important side of it :)
Also by "private" I don't mean completely private Issues. It's perfectly reasonable if site admin could still see such Issues.
I totally agree with you that Jira is not really supposed to be used in that way.
But on the other hand it's much more convenient if you can see all of your tasks in one place, not only projects and operations related ones.
And as the system is so malleable I don't see the reason why not try to accommodate the use-case just as an option. In the end it would be a user's choice whether to use it or not.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

They won't work as you expect because that's not how Security Levels are suposed to work (unless I have missunderstanden you somehow).
You want N security levels for your N users so each user can only see the issues with their security level. Right?
Security levels are actually "tiers" and by "nested" I meant they are in fact a hierarchy, so the higher levels include all the levels below them. That is, if you have the lower security level, X1, and user U1 has that level of privileges he will only see X1 issues... but user U2 with security level X2 (>X1) will be able to see X2 issues aswell as X1 issues.
A project per user doesn't seem quite right... maybe it would be better something radically different like creating a link in jira to an external tool that is actually meant to keep track of this personal tasks. I don't know, the correct decission depends highly on having a deep knowlege about your use case.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

>>You want N security levels for your N users so each user can only see the issues with their security level. Right?
A single Security Level is enough. In a Security Level you can assign permission by Issue roles (Reporter/Assignee), Groups, Project roles and Issue custom fields.
And all you need to make Issue private is to set SL with permissions restricted to Reporter (or additional roles just in case). Once an Issue added with that SL only Reporter will be able to see it. Therefor Issues from different users could be in a single Project in which users can only observe their own Issues.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

How about using Confluence for that?
I assume that some of your tasks are work-related and some are not. You would probably want a friendly link to the work tasks.
With Confluence, you get the nice feature of showing you the task's status, and they have a ton of extensions to manage Jira tasks.
And as for the private tasks, you can define them directly on the page, like: "Call Pizza at 7 PM."

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Get fast answers from people who know.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

Not a Clio customer? Learn more about Clio's Law Firm Project Management Software

Thank you for your feedback. We'll use this information to inform the continual improvement of our self-help resources.

This information is confusing or wrong

This isn't the information that I was looking for

I don't like this functionality

Related articles

How do I Make a Task "Private"?

Key Resources: Task Lists

Can I Set Permissions for Tasks?

Can I Automate Tasks In the Clio Grow Workflow Template?

What Does Each Field In the Add Task Popup Do?

Just click the Chat button in your Clio account!

North America
1-888-858-2546 (toll free)
604-210-2944

Europe, the Middle East, and Africa
+44-800-433-2546 (UK Freephone)
+44-333-577-2546 (UK Mobile Freephone)

We can also be reached via email at support@clio.com for non-urgent matters. We aim to respond within 24 hours or 1 business day.

PRODUCTS

Clio Suite
Clio Manage
Clio Grow
App Directory
Pricing

PRACTICE AREAS

Family Law Software
Civil Litigation Software
Immigration Law Software
Personal Injury Software
Estate Planning Software

Real Estate Law Software
Criminal Law Software
Bankruptcy Law Software
Corporate Law Software
All Practice Areas

FEATURES

Case Management
Software for Office Billing
CRM Software for Legal Firms
Time Tracking for Attorneys
Credit Card Payments

Legal Trust Accounting
Appointment Booking
Client Intake Software
Document Management
All Features

© 2022 Themis Solutions Clio - Legal software Terms Privacy Policy Product Updates

Do you have friends in your network who could benefit from Clio? Earn $250 for every friend that you refer!

Find out how.
A Private Task can only be seen by the Task Creator , the Assignee , and users with the Administrator permission.
CLE ELIGIBLE-WEBINAR Utilizing Technology to Design Efficient Law Firm Processes

Overwatch Buy
How Lesbian
Horny Lingerie

Private Tasks

Report Page