Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Hello, i faced a problem with Jira License related to X-ray

Ali Abdulla telb
September 30, 2023

"Invalid license: Your license subscription is ended. Please renew your Xray license"

Anybody faced this prolem before? and what we can do to complete our activities on Jira normally as all the test cases and test plans dissapeared

Thank you,

 

 

1 answer

0 votes
Derek Fields _RightStar_
Community Champion
October 12, 2018

The Releases issue list is based on Fix Version/s - creating a custom field won't make the issue show up on that list. 

Why do you need a different release custom field from Fix Version/s? 

Serial Founder
October 12, 2018

Hi Derek,

 

Thank you for the response, maybe I am overly anal about the organization of our data but, the Fix/ Version field is currently being used specifically for bug fixes that pertain to a specific version. As we know, all issues are not bug fixes and for new features this field will help me plan a new release by linking the issue (new feature) to a future release.

 

Does this make sense?

Derek Fields _RightStar_
Community Champion
October 12, 2018

You are thinking too narrowly. This field is used to associate the Issue with the Release. Don't think about it as Bug Fixes but as the collection of issues that are associated with this release. 

You should Affects Version/s to identify which Releases are affected by the bug. Since new functionality doesn't affect existing releases, this field will be empty. Use Fix Version/s to indicate which version/s will deliver the issue. This would be the list of bugs and new features that are part of the future release

You can differentiate between bugs and new functionality by Issue Type.

Does this help?

Suggest an answer

Log in or Sign up to answer