Significant Jira Integration Improvements - and Issues with Jira Integration

DevOps Unity Version Control
,
1

Hello team,

I may be missing where some of these features are, in the new Unity DevOps Version of Source Control, but these features seem to be missing that use to be there and I will also request some new features as well for Jira Integration!

1. The Integrations Guide Page is very outdated.

2. Atlassian Jira Extension Tab - Located on the options of a Changeset or Branch No longer exists?

Where do we find our issue information? If this tab/row does not show?

9401459--1315940--upload_2023-10-10_11-32-27.png
9401459--1315940--upload_2023-10-10_11-32-27.png896×563 26.9 KB

3. Create Branch From Issue - Missing Task Type and Description?

  • Task Type is very important. Since 2014 when it seems this extension was made. JIRA has introduced custom task types, as well as SubTasks, and being able to see them in this list below as well as their description would be nice

9401459--1315946--upload_2023-10-10_11-42-2.png
9401459--1315946--upload_2023-10-10_11-42-2.png858×582 29 KB

4. Same Goes for Linking Tasks to Changesets

9401459--1315982--upload_2023-10-10_12-55-46.png
9401459--1315982--upload_2023-10-10_12-55-46.png757×519 25.9 KB

5. Bind Issues to BOTH branches and Changeset Option workflow.

  • With Hierarchal Tasks and Stories we should be able to do both of these workflows
  • Step1 - Create Branch from Normal Task Issue
  • Step2 - Assign SubTask to ChangeSet - mark as In Progress/Open
  • Step3 - When Pushing Commits use Status Transitions to Close SubTasks
  • Step4 - When Merging Use Merge Comment to Cause Status Transitions to Close the Normal Task.
  • Merge Comments do not trigger Status Transitions from my testing. Ill make that Suggestion 6.

6. Merge Comments should allow you to use Status Transitions for the linked branch issue to close them.

  • This will make it where commits can be for Subtasks and Merges be used for Tasks. If Devs decide to use the Both Branch and Change set Option suggestion above.

7. Option in Jira Integration to FORCE issue linking to branches and changesets.
-I imagine if you used the BOTH option listed above these are the steps

  • Step1: When creating a branch you have to select an issue to bind.
  • Step2: Instantly after creating branch a popup will appear to force you to link your changeset to another issue usually a subtask.
  • Step3: Allow an override checkbox that says I choose to not link a task to this changeset. in case there isnt a subtask or special cases you do not want to link a task.
  • Checkbox that allows you to move task to Open/Inprogress upon linking.

8. Status Change Dropdown Instead of Status Transition Text

  • Is there not a way to just have a drop down near the comment of the commit or merge that lets us change the status of our Linked issues? Instead of using text in the commit? Maybe allow both for GUI and non gui users.
    9401459--1315985--upload_2023-10-10_13-28-35.png

9. A easier access link button near your commit or merge comment.

  • See also the image above.

Please feel free to reach out on questions on this. I dont mind getting into a call to discuss in person even if needed.

If these will not get attention unless I use the Feature Submit link. Should I do them one by one?

2

Hi, we appreciate your feedback. I’m sharing it with the product team.
You can also add your feature requests via the following link: https://portal.productboard.com/m8i3g2dqrmywvbqnkdmzeauv/c/819-didn-t-find-what-you-were-looking-for

3

Thank you!, is it most valuable to make a feature request for each individual one?

4

also is there any of these feature requests that are currently working in the new layout of Unity Version Control that I’m just missing somewhere?

5

If it’s all the feedback related to the issue tracker integration, I think it can be done in one single request.

I don’t think any of these requests are available in the Plastic GUI and all of them make sense as improvements.