Add ability to link files/installation scripts to a specific release

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Duplicate
    • None
    • Component/s: None
    • None
    • Environment:
      Standalone

      In today's fast paced environment changes in existing products are very frequent and developers have to roll out new versions. As a windows developer for me standard way to release software is through MSI Scripts. It's a known fact that if we push the responsibility of creating these scripts to a developer then we can reduce the number of bugs which arise due to release processes. This is more true for the applications (And I believe there is a significant amount of these) which are based on extensible Plugin Arhitecture.
      Once the scripts are ready QA/customers needs to be notified whenever there is a new version or a new product release and they need to provided a way to be able to download and install it on their machines.
      Here I want to specify that our users request for private products (which only they know about as these are their tested strategies) so security is also a major concern here.
      As a developer I would always prefer products which can be integrated easily and I do not want to go to different vendors for different needs so that I can focus on my business needs.

      So one critical feature that should be available in JIRA is :

      1.) Provide a facility to link files with the version.
      2.) This should be customizable so that I can put my files in a particular location and whenever I do a "Release" files should be automatically downloadable for that particular version.
      3.) Provide a facility to differentiate between release types (Internal/Public/Private etc.).
      4.) Provide a facility to be able to create "Customer Accounts" who can only see public releases. For private release I should be able to "Select" particular accounts.

      3.)

            Assignee:
            Unassigned
            Reporter:
            Marut Marut
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: