Start Work Page: Default Transition is "Closed" for Projects Without "In Progress"

[MitchTalmadge]

Describe the bug
The default "Transition issue" selection is "Closed" for all of the issues in my repository. There is no way to change the default to the preferred "Developing" (this is our version of "In Progress"). There is also no way to turn the feature off. This leads to accidentally closing the issue often when beginning development.

To Reproduce
Steps to reproduce the behavior:

1. Rename the "In Progress" state to "Developing" in your workflow.
2. Open the "Start work" page for an issue in VSCode.
3. Observe that "Closed" or some other transition may be selected, instead of "Developing".

Expected behavior
I understand that the extension cannot reasonably read my mind to understand which transition I want to use, and that I am not using the default transition names. Therefore, I am requesting a way to define which transition to use by default via the extension settings. Alternatively, or perhaps in tandem, I would like an option to disable the "Transition to" selector by default.

Environment and Version:

• Atlassian Plugin Version (3.8.5)
• Visual Studio Code Version 1.101.2 (Universal)
• Is this a local or cloud environment?
  • Jira is a cloud instance.
  • VSCode is running on macOS, but is accessing a Debian Linux server via Remote SSH.

Additional context

• The transition issue toggle is hardcoded to true by default here:

  atlascode/src/react/atlascode/startwork/StartWorkPage.tsx

  Line 98 in d8c2d6e

  const [transitionIssueEnabled, setTransitionIssueEnabled] = useState(true);

• The code which predicts which transition to use is here:

  atlascode/src/react/atlascode/startwork/StartWorkPage.tsx

  Lines 301 to 309 in d8c2d6e

  	useEffect(() => {
  	// best effort to default to a transition that will move the issue to `In progress` state
  	const inProgressTransitionGuess: Transition =
  	state.issue.transitions.find((t) => !t.isInitial && t.to.name.toLocaleLowerCase().includes('progress')) ||
  	state.issue.transitions.find((t) => !t.isInitial) ||
  	state.issue.transitions?.[0] ||
  	emptyTransition;
  	setTransition(inProgressTransitionGuess);
  	}, [state.issue]);

[MitchTalmadge]

P.S. I am willing to attempt implementing both options if you approve them. :)

[bwieger-atlassian-com]

@MitchTalmadge

Thanks for raising this!

Both of these sound fine. I'm about to go on vacation in a week, so I might pass this off to a colleague to review.

A couple of requirements:

• The default behavior today should not change
• User-provided settings should function across all Jira projects. For example, if a user sets "Very Unusual" as the default transition state, it should apply to the "Unusual" project. If a project doesn't have "Very Unusual" as a state, a fallback option should be available.