I have been trying to reply to an issue but I keep getting an error message:
We're sorry, but the form cannot be submitted due to an expired token. Please copy your content locally, reload the form, and submit your post again.
Question:
Note: I have already tried altering the content and waiting for over 30 min. My response was
I have not populated my test project with it’s own set of issues?
Is the board for your test project referencing the issues in the test project, or is it referencing the issues in the original project? I'd like for it to reference the issues in the original project.
Does making copies of schemes and scheme components mean copying all configurations individually such as issues, types layout screens fields, workflows all separately?
I think I'm trying to do something in an environment that I don't completely understand. I wonder if there's a training on setting up company-owned projects with all it's elements.
The developers are using tasks and subtasks for a larger story. Only the larger story will need to be tested so they don't want the QA to see their tasks and subtasks. Testing for them will be done inherently with the larger story. So they want to end their workflow after the development is done and not have it go through QA. Then QAs workflow would start at "Ready for Test". So I'm trying to come up with solutions for that while knowing just enough to get myself in trouble. I thought of having different task types for QA and Dev with different workflows. Then I thought about somehow flagging dev work and making it a different color and then just having the dev test go to done after they work on it. I am not sure the best path to take here.
I wish I could go premium but our budget just won't allow it.
I will reply in the original post, copying your reply from here for reference.
Usually when you get the "token expired" message refreshing the browser tab will update your token.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.