Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 889079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T13:30:36+00:00 2026-05-15T13:30:36+00:00

JIRA has built in version information, which looks quite handy. However, in an iterative

  • 0

JIRA has built in version information, which looks quite handy.

However, in an iterative model you might release a new version every couple of weeks and that would mean a lot of versions in the lists… which is functional but strikes me as a bit clumsy.

Is this the right way, or are there better approaches in how versions are used in JIRA?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T13:30:37+00:00Added an answer on May 15, 2026 at 1:30 pm

    JIRA lets you “archive” old versions, so they stop cluttering up the interface.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a JIRA environment which already has some information and i'm trying to
How do you version in JIRA when your versions are like 4.8.{TFSBuild}.{TeamCity.Build} ? Do
We use Subversion for version control and Jira for tickets. All our commit messages
I have developed a maven plugin that downloads the release notes from JIRA. It's
Has anyone had trouble with response of JIRA's createIssue method? The problem is, that
I was wondering if there has been any development on the bug http://jira.codehaus.org/browse/GRAILS-2685 ?
In reference to this bug from Sonar: http://jira.codehaus.org/browse/SONAR-1865 and this one (which cross references
I am playing with Weld-SE. I have a project which has pluggable modules. With
I'm using Jira and have been told by the sysadmin that GreenHopper has been
We user JIRA for bug tracking and release management and we have started using

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.