Versions Compared

Old Version 3

changes.mady.by.user Anton Velychko

Saved on

compared with

New Version Current

changes.mady.by.user Anton Velychko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Recent Updates

Features

  • Enabled o1-mini and o1-preview OpenAI models: Access new models to enhance AI capabilities.

Expand
titleNotes

New models full configuration is not available yet. Only max tokens could be set.

Note

If you use a personal API Key, your usage Tier should be at least level 3 to have access. Learn more

  • Introduced branches for chats: Manage conversations more effectively by utilizing branches.

  • Added a "Try again" button: Generate one more step response from AI on a different branch.

Expand
titleIn-app view and notes
image-20241004-091702.pngImage Added
Info

The 'Try again' button is now available exclusively for step responses. When used, the full chat history will be sent, new branch created, but the remaining steps will remain unprocessed.

Feature extension for “continue scenario using this response“ is currently in development.

Improvements

  • Steps validations: Implemented validations for creating, updating, and debug running scenario versions.

  • Model pricing: Added pricing information for models in AI Settings for better transparency.

Expand
titleIn-app view and notes
image-20241004-092333.pngImage Added

Pricing is calculated based on the amount of AI data processed, including both input (requests) and output (responses), and is charged per 1 million tokens. Approximately 1 token equals 4 characters.

Prices are determined using predefined internal data and may become slightly outdated if the AI provider updates their rates

  • Improved prompt for Summary scenario: More specific description to avoid confusion with other contexts and the word "summary".

Expand
titleUpdated prompt

Analyze the context of the given Jira issue or feature, focusing specifically on the key objectives, description, and core purpose of the 'Issue'. Disregard unnecessary details unless they are directly related to clarifying or enriching the core issue. Secondary information (subtasks, linked issues, project details, Confluence pages) should only be used if it adds direct value or helps refine the main context.

Based on this core information, create a set of action-oriented titles or summaries, designed to communicate the intent and solution direction of the issue. Use the following six title styles, ensuring each title is concise and no longer than six words:

  1. Current Title (Rephrase the existing title, making it clear and concise).

  2. Job To Be Done (Express the job or outcome the user aims to achieve).

  3. User Story (Frame it as a user story, focusing on who the user is and what they need).

  4. Feature (Highlight the feature or enhancement to be developed).

  5. Simple and Direct Title (A straightforward title describing the action or feature).

  6. Creative, Inspirational Style (A catchy or inspirational title to motivate the team).

Generate three versions for each of these six styles and briefly explain which type of context or scenario each version would be most appropriate for (e.g., for stakeholders, for team alignment, for user-facing documentation, etc.)

UI Updates

  • Header panel for messages: Added a header panel to messages that displays title, price, and "Try again" button.

Bug Fixes

  • Scenario button issue: Fixed an issue where the "Add scenario" button disappeared once all scenarios were deleted.

  • Disabled unsaved scenario runs: Prevented running a new scenario without saving to ensure data integrity.