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

Feature Request- Add task = add person #1564

Open
Talishask opened this issue Oct 22, 2019 · 5 comments
Open

Feature Request- Add task = add person #1564

Talishask opened this issue Oct 22, 2019 · 5 comments

Comments

@Talishask
Copy link

@Talishask Talishask commented Oct 22, 2019

Creating this issue based on a recent email from Giacomo:
Long standing issue: when we add a task (a person) to a workshop, if the person is not already in the DB, we need to move to the ‘add person’ form, add the person there, return to the workshop, add the task.

This might have had sense when we were aspiring at having a detailed profile of any person in the database. However, since we are more and more often adding persons with just their names, I wonder if a way could be implemented so that adding a new task (person) to a workshop, automatically add the person in the database!

Talisha: I too experience this issue. I'm currently using a text editor as a work around.

@pbanaszkiewicz
Copy link
Contributor

@pbanaszkiewicz pbanaszkiewicz commented Nov 7, 2019

The strange thing is that the code is supposed to create a new person when there's no match from DB.

I think this is a bug and I may need a sample input CSV file that doesn't allow to create persons.

EDIT: I misunderstood Giacomo. I thought he had meant the bulk upload feature. In case of changing add task form, it's not a bug - it's a feature! I'll provide timespan required for me to implement this change.

@pbanaszkiewicz
Copy link
Contributor

@pbanaszkiewicz pbanaszkiewicz commented Nov 7, 2019

Update on the feature request: I will need to know if you want to ditch the old interface ("person", "role", instructor training seats) and use only the new one ("person name", "person last name", "person email", "role", instructor training seats), or combine both ways of adding a task.

@maneesha
Copy link
Contributor

@maneesha maneesha commented Jan 14, 2020

@pbanaszkiewicz can you clarify what you mean by the old and new interface?

@pbanaszkiewicz
Copy link
Contributor

@pbanaszkiewicz pbanaszkiewicz commented Jan 14, 2020

@maneesha when adding a task to the workshop you have these fields:
obraz

This is the current ("old") interface. It assumes a person already exists for this task.

But @gperu & @Talishask want to add tasks when persons don't exist, which means we have to create them. So in the "new" interface we'd have to replace "Person" field with three fields required to create a person: personal name, family name, and their email. However, if we do that, we lose that "old" functionality to add a task for existing person.

Here's what I need to know: how do you see this implemented?

@Talishask
Copy link
Author

@Talishask Talishask commented Jan 17, 2020

Hi @pbanaszkiewicz ,

We enter tasks at two points in our workflow, when we are notified about the workshop and create the event and after the event has occurred.

Currently, when a person is not in the database we need to:

  • Open 'New Person' in a new window
  • Add the individual's information and submit the person
  • Return to the event edit page
  • Add task in the event
    We have found a workaround to this by recording information for persons not already in AMY in a csv for bulk upload. It's still additional work but not as tedious as adding the person each time.

We would still hope to have the current functionality to add a task for an existing person, but if the person is not in AMY we need to add the person into AMY in order to add the task. More frequently, we are adding individuals without an email address. So we are hoping that the add a task function would also allow us to add a person if the person is not currently in the database. When adding a task, would it be possible to:

  • have the 'Person*' field function the same, but if the name is not recognized a 'New Person?' option appears in the list?
  • then when we select 'New Person?' three fields pop up under the 'Person*' field for us to add the information for the new person (Personal (first) name*, Family (last) name, and Email address)
  • When we press submit it creates the person and adds the task

not sure if that's an option or but maybe?

@pbanaszkiewicz pbanaszkiewicz added this to the v2.11 milestone Jan 20, 2020
@pbanaszkiewicz pbanaszkiewicz removed this from the v2.11 milestone Feb 24, 2020
@pbanaszkiewicz pbanaszkiewicz added this to the v2.12 milestone Feb 24, 2020
@pbanaszkiewicz pbanaszkiewicz removed this from the v2.12 milestone May 2, 2020
@pbanaszkiewicz pbanaszkiewicz added this to the v2.13 milestone May 2, 2020
@pbanaszkiewicz pbanaszkiewicz removed this from the v2.13 milestone Jun 21, 2020
@pbanaszkiewicz pbanaszkiewicz added this to the v2.14 milestone Jun 21, 2020
@pbanaszkiewicz pbanaszkiewicz removed this from the v2.14 milestone Sep 2, 2020
@pbanaszkiewicz pbanaszkiewicz added this to the v2.15 milestone Sep 2, 2020
@pbanaszkiewicz pbanaszkiewicz removed this from the v2.15 milestone Dec 6, 2020
@pbanaszkiewicz pbanaszkiewicz added this to the v2.16 milestone Dec 6, 2020
@pbanaszkiewicz pbanaszkiewicz removed this from the v2.16 milestone Jan 28, 2021
@pbanaszkiewicz pbanaszkiewicz added this to the v2.17 milestone Jan 28, 2021
@pbanaszkiewicz pbanaszkiewicz removed this from the v3.0 milestone May 27, 2021
@pbanaszkiewicz pbanaszkiewicz added this to the v3.1 milestone May 27, 2021
@pbanaszkiewicz pbanaszkiewicz removed this from the v3.1 milestone Jun 8, 2021
@pbanaszkiewicz pbanaszkiewicz added this to the v3.2 milestone Jun 8, 2021
@pbanaszkiewicz pbanaszkiewicz removed this from the v3.2 milestone Jul 3, 2021
@pbanaszkiewicz pbanaszkiewicz added this to the v3.3 milestone Jul 3, 2021
@pbanaszkiewicz pbanaszkiewicz removed this from the v3.3 milestone Aug 21, 2021
@pbanaszkiewicz pbanaszkiewicz added this to the v3.4 milestone Aug 21, 2021
@pbanaszkiewicz pbanaszkiewicz removed this from the v3.4 milestone Jan 3, 2022
@pbanaszkiewicz pbanaszkiewicz added this to the v3.5 milestone Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants