Frequently Asked Questions

“So storywise is just an AI wrapper, right?”

No, storywise is far more than just an AI wrapper. While storywise does integrate AI capabilities to enhance the requirements engineering process, it’s a comprehensive software solution designed specifically for creating, managing, and communicating software requirements effectively.

What makes storywise different from a simple AI tool?

storywise offers a complete requirements management system with features like:

Structured filing system for organizing requirements and maintaining cost control
Version control and comparison to track changes between different specification versions
Inheritance of acceptance criteria across related requirements
Customizable document output in Word or PDF formats
Integration with project management tools like JIRA
Linking capabilities for mockups, effort estimates, and related entities
Keyboard shortcuts for efficient navigation and editing
Comprehensive cost tracking across the entire project

Why can’t I just use a generic AI tool to write my requirements?

Generic AI tools lack the specialized structure, workflow, and integration capabilities that storywise provides. While they might help draft text, they don’t offer the complete ecosystem needed for professional requirements management, version control, team collaboration, and seamless handoff to development teams.

Is it possible to map the “Definition of Done”?

Yes, storywise fully supports “Definition of Done” mapping through several features:

Customizable acceptance criteria for each user story
Ability to attach images and mockups directly to requirements
Integration with design tools like Figma through links
Detailed descriptions that can clarify completion criteria

Are Jira-edited User Stories and Epics synced back to storywise?

Yes, we support bi-directional synchronization with Jira. The backend functionality is already implemented and we’re expanding it to provide even better integration with existing projects. Specifically:

You can download epics and stories from Jira into storywise
Our system intelligently merges your storywise stories into existing Jira epics
The system preserves the relationship between requirements in both systems

Can the format of “Acceptance Criteria” be changed, e.g., to bullet points?

Currently, this is not supported. The acceptance criteria format is standardized to maintain consistency across projects, but you can always use the description as you like.

Can test cases be automatically derived from storywise + acceptance criteria?

This feature is not currently available. We’re looking for test customers to help us develop this functionality - please contact us if this would be valuable for your organization.

Is there a way to automatically group user stories that logically belong together across multiple epics as features?

Automated grouping isn’t available yet, but you can manually group related stories. This manual grouping is fully supported in:

Exports to documentation
Jira/Azure/Devops integration
Price information summaries
Version comparisons

How does storywise represent dependencies and releases, for example, to define an MVP?

storywise includes a comprehensive release management system where you can:

Assign tickets to releases
Group requirements by release in exports (docx, project management tools like jira)
Filter price information by release
Include release information in Jira synchronization
Compare versions with different releases switched on/off

Is storywise limited to the “User Stories” documentation format?

No, storywise is flexible in its documentation approach. In addition to structured user stories, you can use a less structured “requirements text” format where you can simply add text without adhering to the user story structure.

Can I reorder and move items around?

Yes, you can easily reorder and move items. Look for the three dots button at the top left of the table interface, which provides access to reordering, moving, and other organizational functions.

Can I add my own prompts?

This feature is coming very soon and is nearly complete. You’ll be able to add context specific to your company and even more granular context for each individual project, allowing the AI to generate more tailored and relevant suggestions.

Project sharing in Storywise is organized at the organization level. This means that visibility works as follows: either everyone in an organization can see a project, or no one in that organization can see it. You cannot scope access to individual users within an organization - it’s all or nothing.

Best Practice: Create Projects in Your Own Organization

The recommended approach for collaborating with external organizations is:

Create projects in your own organization - This allows you to:
- Share AI tokens and library resources across all your projects
- Maintain consistent settings and integrations (Jira, Figma, etc.) across your work
- Have full control over project management
Invite other organizations to specific projects - Once your project is set up in your organization, you can invite external organizations to collaborate on that specific project. They will have access only to that project, not your entire organization. When inviting, you can choose whether they see only public documents (for comparison offers or limited collaboration) or all documents (for full co-working experiences).

Why This Approach Works Best

Resource sharing: Your organization’s AI tokens, document library, and settings are available across all your projects
Selective collaboration: External organizations only see the projects you explicitly invite them to
Clear boundaries: Each organization maintains its own settings, integrations, and resources while collaborating on shared projects

What if I Created a Project in the Wrong Organization?

If you’ve already created a project in the wrong organization, you’ll need to contact support to migrate the project between organizations.