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

Google sheets connector pivot table properties can be specified only via datamapper #4500

Closed
mmelko opened this issue Feb 11, 2019 · 3 comments
Assignees
Labels
cat/enhancement Enhancements to existing features and capabilities closed/migrated notif/uxd Ping UX team that UX related changes are involved prio/p1 The priority of a bug. p1 means high source/qe Raised by QE status/never-stale Marker that this issue should not be marked as stale target/7.x zenhub/backlog

Comments

@mmelko
Copy link
Contributor

mmelko commented Feb 11, 2019

See also https://issues.jboss.org/browse/ENTESB-11484

This is a...


[x ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Documentation issue or request

Description

I might be missing some context to pivot tables but I believe it's not the best option to setting up the pivot table only via data-mapper custom properties (see demo (here). From my pov it's mainly pivot table configuration and the best would be to configure it during connection settings via some form. This would be probably better from UX perceptive too.

On the other hand ability to overwrite privot table properties via DM is also nice.

Here is basically only pivot table configuration with no real mapping(except spreadsheetId):
screenshot_20190213_105321

@mmelko mmelko added source/qe Raised by QE cat/enhancement Enhancements to existing features and capabilities labels Feb 11, 2019
@pure-bot pure-bot bot added the notif/triage The issue needs triage. Applied automatically to all new issues. label Feb 11, 2019
@mmelko mmelko added the notif/uxd Ping UX team that UX related changes are involved label Feb 13, 2019
@tplevko tplevko added the prio/p1 The priority of a bug. p1 means high label Feb 14, 2019
@heiko-braun heiko-braun removed the notif/triage The issue needs triage. Applied automatically to all new issues. label Feb 14, 2019
@heiko-braun heiko-braun added this to the Sprint 43 (4/4) milestone Mar 11, 2019
@heiko-braun heiko-braun removed this from the Sprint 43 (4/4) milestone Apr 1, 2019
@stale
Copy link

stale bot commented Jun 30, 2019

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale Issue considered to be stale so that it can be closed soon label Jun 30, 2019
@stale stale bot closed this as completed Jul 7, 2019
@heiko-braun heiko-braun added the status/never-stale Marker that this issue should not be marked as stale label Jul 7, 2019
@heiko-braun heiko-braun reopened this Jul 7, 2019
@stale stale bot removed the status/stale Issue considered to be stale so that it can be closed soon label Jul 7, 2019
@heiko-braun heiko-braun added this to the Sprint 50 (1/4) milestone Jul 30, 2019
@amysueg
Copy link

amysueg commented Jul 30, 2019

@dongniwang Can you take a look at this one? thanks.

@heiko-braun
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cat/enhancement Enhancements to existing features and capabilities closed/migrated notif/uxd Ping UX team that UX related changes are involved prio/p1 The priority of a bug. p1 means high source/qe Raised by QE status/never-stale Marker that this issue should not be marked as stale target/7.x zenhub/backlog
Projects
None yet
Development

No branches or pull requests

5 participants