ask-jira
ask-jira copied to clipboard
Python app that uses the Jira API for aggregate and complex tasks and reports
Since Jira automatically assigns ticket IDs in the order of their creation, it is not easily possible to perserve the IDs from the source Jira project in the target Jira...
How about something like this?
A bit of configurability to the new portfolio-epics feature: * Detect if sub-epics already exist. If so, create link only, do not create new copies * Configurable search direction for...
Add new config option for mapping custom single value fields, like single selects (that have {'value':x} structure.
No change in documented behaviour, but allows partial config, if not interested in fully mapping everything. * Fixed if, won't fail if transition is not found, but continues as originally...