Private Area for Tasks

[Lukas Rabe]

How can i create an area for Tasks for myself? Without any connection to a project.

[Beth Schaefermann]

I thought this was an interesting idea and pushed an internal discussion on whether a personal project would be attractive to our users.

We have a support project set up where reporters can only see their own tickets. We could set up an additional project with a similar configuration and call it something like "My personal project." Then only sys admins and the individual users could see the issues they create in their personal project without having to set up a billion personal projects. The versioning scheme could just be weekly versions.

Then people could see their personal tasks in context of their work tasks. I think that would work...

[Beth Schaefermann]

Some feedback:

"Please do this! I think about how nice it would be to have this for personal tasks every time I go into Jira, for exactly the same reasons you listed—adoption (you’re in there all the time, so put it all in one place), avoiding extra tools (get this stuff off of scraps of paper or Outlook tasks), etc. Even if people didn’t use it for their personal non-business tasks, I see value in being able to use it for things like change benefit elections, check my vacation balance, review my objectives for the year, change 401k contributions, change address in Oracle, etc. My only concern would be making it clear who has access to see the projects/tasks."

My response: "It would have the same security scheme as the Atlassian Support Project. So on every ticket there would be red text that read "Reporters and Atlassian Tools Support (Reporters and the Atlassian Tools Support can access these issues)" <--Note we call our JIRA-Admins "Atlassian Tools Support"

[Nic Brough -Adaptavist-]

The basic trick behind it is to create a project where the permissions say "browse = reporter browse only" - that's a special flag you have to enable in a config file.

[Beth Schaefermann]

I am going to test it out on staging next week and will report back on how it goes. The other concern reported was defaulting the Assignee to the reporter and limiting issue assignment to the reporter, which likely translates to creation of a separate permissions scheme instead of direct re-use of the support project's permissions scheme.

[Steven Bonfante]

I know the original string on this subject started a while ago but did anything ever come if it?

[Nic Brough -Adaptavist-]

Nope.  People used a to-do project as above, or Trello

[David Gray]

Is that working? What are the pros & cons? It seems like the best alternative, but before rolling that out to the company (on my third week) I want to make sure I've thought it through.

[Nic Brough -Adaptavist-]

You can't create issues outside a project.

With a bit of tinkering, you can create a project that will act as a private to-do list for anyone who needs it though.

[Lukas Rabe]

Ok thank you :)

[Gregory Schwedock]

Here's a deeper dive into this idea and all the permissions settings to use.