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.

Sign up for GitHub

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

Jump to bottom

Handle ticket merges #9

Open
tom-coward opened this issue May 26, 2020 · 1 comment
Open

Handle ticket merges #9

tom-coward opened this issue May 26, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@tom-coward
Copy link
Contributor

Handle the changing of the resource ticket_id key if necessary on ticket merge.
@tom-coward tom-coward added the bug Something isn't working label May 26, 2020
@tom-coward
Copy link
Contributor Author

Need to consider best way of handling this situation. It's possible that the merged tickets (of which there could theoretically be an unlimited amount) may each already be associated to different resources, so some form of confirmation of which resource to associate to the one ticket after merge would be required.

@tom-coward tom-coward added enhancement New feature or request and removed bug Something isn't working labels Jun 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tom-coward