[PoC] Create issue with Jira AI #431
Conversation
sdzh-atlassian
requested review from
bwieger-atlassian-com,
cabella-dot,
marcomura,
akalia-atlassian and
pastelsky
as code owners
| @@ -170,6 +170,10 @@ export function useEditor<T extends UserType>(props: { | |||
| const view = useRef<EditorView | null>(null); | |||
| const [content, setContent] = useState(props.value || ''); | |||
|
|
|||
| if (props.value !== content) { | |||
There was a problem hiding this comment.
Not sure if we still need this here, might need feedback from @cabella-dot
There was a problem hiding this comment.
Yeah no need for this. Will have to revisit when we want to implement this editor
sdzh-atlassian
force-pushed
the
poc/create-issue-with-ai-prod-2
branch
from
96c04a8 to
dc84de6
Compare
sdzh-atlassian
force-pushed
the
poc/create-issue-with-ai-prod-2
branch
from
dc84de6 to
236ac9f
Compare
There was a problem hiding this comment.
why is this file necessary?
| "description": "Enables AI-assisted issue suggestion for TODO comments", | ||
| "scope": "window" | ||
| }, | ||
| "atlascode.issueSuggestion.contextLevel": { |
There was a problem hiding this comment.
didn't we decide to cut this choice leaving "codeContext" as the only way?
|
|
||
| return responseData; | ||
| } catch (error) { | ||
| console.error('Error fetching issue suggestions:', error); |
There was a problem hiding this comment.
| console.error('Error fetching issue suggestions:', error); | |
| Logger.error(error, 'Error fetching issue suggestions'); |
| }, | ||
| }); | ||
|
|
||
| const buildRequestHeaders = (authInfo: BasicAuthInfo): any => ({ |
There was a problem hiding this comment.
I think you can type this as Record<string, string>
| @@ -171,7 +171,7 @@ export function registerCommands(vscodeContext: ExtensionContext) { | |||
| } | |||
| }, | |||
| ), | |||
| commands.registerCommand(Commands.CreateIssue, (data: any, source?: string) => createIssue(data, source)), | |||
| commands.registerCommand(Commands.CreateIssue, async (data: any, source?: string) => createIssue(data, source)), | |||
There was a problem hiding this comment.
I'm curious about this change
| } | ||
|
|
||
| static async getSuggestionAvailable(): Promise<boolean> { | ||
| const isFeatureEnabled = FeatureFlagClient.checkGate(Features.EnableAiSuggestions); |
There was a problem hiding this comment.
if this is false, return immediately like you did in getSuggestionEnabled, so we don't waste resources spawning the configuration promise
| error: '', | ||
| }; | ||
| } catch (error) { | ||
| console.error('Error fetching issue suggestions:', error); |
There was a problem hiding this comment.
| console.error('Error fetching issue suggestions:', error); | |
| Logger.error(error, 'Error fetching issue suggestions'); |
| // TODO: actually send an analytics event | ||
| window.showInformationMessage(`Thank you for your feedback!`); | ||
| } catch (error) { | ||
| console.error('Error sending feedback:', error); |
There was a problem hiding this comment.
| console.error('Error sending feedback:', error); | |
| Logger.error(error, 'Error sending feedback'); |
|
|
||
| case 'aiSuggestionFeedback': { | ||
| handled = true; | ||
| const { isPositive, todoData } = msg as any; |
There was a problem hiding this comment.
this casting of msg to any looks sus... why isn't the typing working?
sdzh-atlassian
changed the title
What Is This Change?
This is the POC integration of the issue-creating ai agent into the TODO workflow :)
This version is not intended for broad audience yet for a variety of reasons, but we can use it to do some internal testing :)
How Has This Been Tested?
Basic checks:
npm run lintnpm run test<- addressed, but [AXON-385] chore: fix jest config to work with src/ paths #432 solves the underlying issue with tests hereAdvanced checks:
If Atlassian employee & Bitbucket changes: did you test with DC in mind? See InstructionsN/ARecommendations:
Update the CHANGELOG if making a user facing changeN/A