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

[15.0][MIG] website_event_questions_by_ticket: Migration to version 15.0 #307

Merged

Conversation

stefan-tecnativa
Copy link
Contributor

cc @Tecnativa TT42045

@chienandalu please review!

pedrobaeza and others added 10 commits March 23, 2023 10:54
This module allows to set that an event question is only asked for certain
tickets.

If the question is general, then having one of the allowed tickets will serve
for showing it. If the question is specific to each attendee, then the
evaluation will be done for each of the tickets.

Configuration
=============

1. Go to *Events > Events*
2. Create or select one event.
3. On the "Questions" page, create a new question or edit an existing one.
4. Fill the field "Limited to tickets" for restricting the question to that
   ticket. Leave it blank for making it available for all tickets.

Usage
=====

1. Go to the website.
2. Go to "Events" section and select one of them.
3. Select ticket quantity and click on "Register".
4. On the popup dialog, the questions linked to that ticket and those without
   restrictions will be shown.

Known issues / Roadmap
======================

* Add tests (tour) to the module.
Currently translated at 100.0% (4 of 4 strings)

Translation: event-13.0/event-13.0-website_event_questions_by_ticket
Translate-URL: https://translation.odoo-community.org/projects/event-13-0/event-13-0-website_event_questions_by_ticket/es/
@stefan-tecnativa stefan-tecnativa force-pushed the 15.0-mig-website_event_questions_by_ticket branch from 17fb35d to 7499764 Compare March 23, 2023 10:51
@pedrobaeza
Copy link
Member

Have you seen #289 ?

@stefan-tecnativa
Copy link
Contributor Author

Have you seen #289 ?

No, I didn't know this PR existed.

@pedrobaeza
Copy link
Member

You have to search first if there's an open PR before starting with the development.

@stefan-tecnativa
Copy link
Contributor Author

It would be correct to merge this PR as #289 hasn't been active with the reviews?
Or instead close this PR and superseed the other PR, as it was opened first?
ping @pedrobaeza

Copy link
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ocabot migration website_event_questions_by_ticket
/ocabot merge nobump

@OCA-git-bot OCA-git-bot added this to the 15.0 milestone Jul 5, 2023
@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 15.0-ocabot-merge-pr-307-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot mentioned this pull request Jul 5, 2023
16 tasks
@OCA-git-bot OCA-git-bot merged commit 2918340 into OCA:15.0 Jul 5, 2023
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 7064f20. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants