Creating an arbitrary date field unrelated to data to hold every date that exists
I'm trying to recreate a chart that compares Created to Resolved issues (based off JIRA data). How it looks in JIRA below
Where i'm running into trouble in Domo is that I think JIRA just creates a random new date field/range on the fly that isn't included with the data when pulled over. In Domo I have to choose what field to plot the X axis with. In JIRA it's setup to show Last 180 over both date fields (Created Date, Resolved Date). So if I set the Domo X axis to Created the resolved number is off because although the JIRA ticket was resolved on July 9th if it was created longer than 180 days ago it's not included.
Is there some way I can just have a date field with all dates that I can use to chart the X axis then just use the count of created and count of resolved as series? I believe this would give me exactly what I'm looking for. Preferably as a Beastmode/Calculated field instead of a Dataflow but if Dataflow is all that is possible I'll go that route as well.
Also it doesn't appear a MySQL dataflow will be possible as I run into this error "
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**
Best Answer
-
Please up-vote my idea here:
https://dojo.domo.com/t5/Ideas-Exchange/Display-quot-empty-quot-Date-values/idi-p/27318
I have the same issue
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman1
Answers
-
Is anyone able to help out with this request?
0 -
Help!
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**0 -
Please up-vote my idea here:
https://dojo.domo.com/t5/Ideas-Exchange/Display-quot-empty-quot-Date-values/idi-p/27318
I have the same issue
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman1 -
Done, I didn't realize one existed and had also created an idea
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**1 -
FYI, just adding on the solution - to solve the error "Identifier name must be 64 characters or less" in MySQL, one feasible way around is to use Magic ETL to rename that column to create a new Dataset so that can be used in the MySQL Dataflow!
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 738 Beast Mode
- 56 App Studio
- 40 Variables
- 684 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 123 Manage
- 120 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive