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

Epic Not Resolving in Google Sheet #230

Open
skorecki opened this issue Jul 31, 2019 · 3 comments
Open

Epic Not Resolving in Google Sheet #230

skorecki opened this issue Jul 31, 2019 · 3 comments

Comments

@skorecki
Copy link

The Epic is never resolving after the table is generated in Sheets.

Steps to Recreate

  1. Define a query that includes Epic
  2. Confirm Custom functions are enabled
  3. Create Issue Table from Filter from step 1

Actual Results
Epic values show #ERROR: The document owner (you) must enable custom functions... (See attached screenshots)

Expected Results
The correct Epic value is populated in the issue table

2019-07-31 08_30_05-Project Aid for Jira - Settings
2019-07-31 08_26_30-Project Aid for Jira - Epic ERROR

@ljay79
Copy link
Owner

ljay79 commented Jul 31, 2019

Hi @skorecki is the document owned by yourself or by someone else?
The "Epic" field is enabled under "Configure Custom Fields" ?
jst-epic-field

If you are unable to resolve the issue by yourself, please allow me to have some debug logs available:
Please activate Debugging in "About" dialog, provide me with your "Temp. User Key" and then perform at least one another try. This way it will log the error and debug information to my StackDriver logging account where I can analyze it better.

Note: User credentials are not transmitted in any log data.

@skorecki
Copy link
Author

skorecki commented Aug 1, 2019

I do own the document and do have the Epic field in my Custom Fields

2019-08-01 15_57_23-Project Aid for Jira - Custom Fields

I have run this query at least a couple of times today with logging enabled.

Temp. User Key:
AANBUuUpTbBWKPCJpe1BmioisZPoaFzKSkBoCTVHA1kqBCXGi5WMwkLSKyhZoQbU/niR4GCP7h7h
Environment:
Production, Logging enabled

@ljay79
Copy link
Owner

ljay79 commented Aug 1, 2019

Hmm its very strange. The logs appear ok.
The shown message/error is a simple validation of a single setting/options. So something appears fishy that it cant fetch the correct value as your screenshot shows, the option is enabled.

Do me a favor and uninstall the add-on, close all chrome windows, then start and install the add-on again.

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