Categories: does the AI create the categories automatically, or does the user need to create the categories first and the AI then organizes the requirements accordingly?
The AI only assigns requirements to categories; you will need to manually create the categories yourself. We chose this path for two reasons. First, we think that many SIs have common categories that they use over and over again across projects, so you may only need to create them once and then you can re-use them as you go forward. And second, we have found that many people have different ways of organizing requirements. Initially I thought this would be simple (ha!) - but some people like to organize by user function, and some like to organize by the internal teams that will be delivering the work. A few other notes:
The more detail you add to a category description, the better the assignments will be
You can manage your organization-wide categories from the Categories tab in your org; you can manage your project-specific categories from the Categories tab within a project
Jira integration: is the sync a nightly job?
Yes.. and also realtime. First, when you initially select "send to Jira," we send information from Glossa to Jira in real time. And then if you select the option for "Override Jira overnight" in your project configuration settings, we'll send any updates that you made in Glossa to an already synced Jira ticket overnight, potentially overwriting what's already in Jira.
You can learn more about the Jira integration here.
Requirement order: How are requirements ordered in the requirements list?
They are ordered based on the source data imports.
Additional sources: If additional sources are added to a project, will existing requirements automatically update to reflect the new related notes?
As additional sources are added, we create new requirements from those sources. Then we flag related requirements so that you can review/merge as needed. We thought this was a much safer approach for now, so we don't make too many assumptions and potentially overwrite important requirements.
(One thing to note: we DO combine requirements from the same source file. So if you're in a meeting and you talk about a specific topic in the beginning of the conversation and also at the end, we would create just one requirement from that content)