As the 'branch' Ivy property is also mandatory for my organization, I'm willing to try to modify the source of Gradle to make it work, but I'd like to known if what I'm trying to do may collide with the new dependency DSL ? Or, in other words, is the branch feature planned for the new dependency DSL as a side effect of the rewrite of the DSL ?

Any progress on this?
Or is there workaround for following scenario:
Let project X has one main branch 2.x and one maintenance branch 1.x
How do I specify that project Y depends on latest release version of branch 1.x (in other words how do I specify filter on version number such as 1.2.+ and also module status?).

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

The issue is now tracked on GitHub: https://github.com/gradle/gradle/issues/1357