Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add and name people who aren't users for planning or scenario development #548

Open
georgiamoon opened this issue Jan 3, 2025 · 4 comments

Comments

@georgiamoon
Copy link

It'd be really helpful to be able to add and enter data for our team, so that they can review it and/or so we can maintain it as a planning tool, and consider scenarios/options.

Example user story:
A new project opportunity means that we could shift around team allocations and bring on a collaborator, but we want to game it out before engaging the whole team to think about it

@jsonin
Copy link
Contributor

jsonin commented Jan 3, 2025

Agree.

We had a "TBD" in the pull-down for scenario planning... and stubbing out possible people.
I lost that somewhere in the shuffle. Will add it in pronto.
image

@georgiamoon
Copy link
Author

georgiamoon commented Jan 3, 2025

@jsonin it's still in one of the modal views, I saw that. I guess I was thinking more like — I'll add my full team, but they don't have to be users and I can model out some options for team/project distribution. So one TBD is good, but I'm thinking, like 2 people are users and we can provisionally add our whole team to make a plan / explore some options. So I think it'd be a few features:

  • Add people without needing to add them as users
  • Put labels/names on placeholder people
  • Have scenarios, e.g. Options of "Staffing Plans"

Another option, if you can add arbitrary people who aren't users is that you could have "Georgia-Option1" and "Georgia-Option2", etc and that'd allow you to develop scenarios to compare.

@jsonin
Copy link
Contributor

jsonin commented Jan 3, 2025

That's an understandable and needed scenario.
A looks-like model for a Georgia or Juhan or whoever... that can be planned against, and then turned "real" with an invite, that's then attached to that synthetic instance.

I get it. And dig it.
We'll work it.

Maybe a stop-gap is

  1. naming the TBD person
  2. adding a bunch of named TBD people to projects (that aren't full accounts/real people yet)
  3. when you're ready to add the team, add real people... and then assign that Georgia-Option1 to the real Georgia via the pull down.

We have 2+3. We can add 1.

@georgiamoon
Copy link
Author

Cool, yeah it seems like a more advanced feature, but also very doable with the current experience and features.

Cool 👍🏼👍🏼

@jsonin jsonin mentioned this issue Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants