To further expand on this, Currently, we create Tasks in Clarizen and sync them to JIRA as Epics. We are going to sync any sub Issues (stories) back under the Epic created from Clarizen. The specific use case is for passing Project related development work into JIRA so Development can work on it.
Our development team also has their own Epics and Stories they create in JIRA which are not related to projects but product and that we have no desire to move into Clarizen.
So, I created a Mapping and Event to push my Epics, and I created a Mapping and Event to Pull my Stories. The problem is, there is no way to filter out the Sub Issues (Stories) that are tied to Epics that were created in JIRA and NOT in Clarizen. Visual at the bottom.
I have to believe this is standard use case the majority of the time. If an organization is using JIRA and Clarizen simultaneously, it is because their developers are using JIRA and Clarizen is managing project work. If they invest in the integration it is because they need to pass Project work, bugs, Requests, etc, to their developers. I would also guess that their developers aren't just sitting around waiting on issues to come over from Clarizen but have Roadmaps, Epics and Stories they are working on that may not (probably are not) in Clarizen. Or I am way off. Either way, would be nice to have.
A few ways this could be handled:
1) Enable the ability to use nested filters on the events
Ex. Epic.Clarizen ID is not null
Ex. Parent.Clarizen ID is not null
2) Add mapping of related Items: Sub Issues
3) Create a webapp (could probably add this to iHub) to do the following
1. web hook on create issue that calls this new webapp with info on the issue
2. web app parses out clarizen id and parent epic id
3. web app posts back to jira to update the clarizen id on the story
*Basically, update sub items in JIRA based on previously synced issues
Comment actions