I know there is a limitation where users cannot see tickets that are moved from the service desk 'project' to an internal development project.
We were thinking of creating a 'duplicate' issue in the development project and linking it to the original service desk issue as a way of tracking. Has anyone tried this, how well does it work?
Is anyone successfully using any other work-arounds? We're open to suggestions
A far better and more logical way would be that Atlassian reconsiders/rethinks the "agent-collaborator" licence policy: if collaborators (ie. JIRA licenced users) would have the possibility to actively work on SDesk issues (ie. logging work, be the assignee etc... like it works in "normal" non-SDdesk JIRA projects, then the world would look better for erveryone: the traditional JIRA customers would LOVE Sdesk and use it heavily, Atlassian would have a GREAT product in their product portfolio that could be a major competitor for the traditional/large SDesk systems arround (BMC, IBM, HP, etc...).
Just my 2 cents ...
Hello Community 👋, I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events