Status:
1. I am doing a trial offline (Ubuntu) of Jira Core and Jira Software
2. created a profile on Jira Cloud (Core+Software+Confluence) that plan to use for publications of templates of projects
3. for the time being, I am doing some sample testing of the various options
4. personal background: methodology and software since the 1980s, cultural&organizational change since the 1990s (along with data-driven initiatives)
Business case:
The solution currently proposed, to export all, create a new instance, remove what is not needed is unnecessarily complex
I saw that some suggested "project configurator for Jira", but, as the API is avaiable, I wonder if somebody is already working on a plugin that is able to "mirror" the whole access to information stored into an instance, and selectively choose what (including metadata) should be in an export
For now, my idea is only to create sample projects to share freely as exports via Github and publications, but actually could be useful to some companies working on projects "resell" their best practices
As the cloud offer of Atlassian now gives the service for free for smaller teams, this could actually enable some of them to "specialize" and reshare specific "project-based solution" that cannot simply be automated (eventually up to licensing), without need for them to expand their own staff, as it happened in other domains (e.g. used similar approaches in the past to deliver both projects and training in specific domains)
Within larger companies, it could be useful e.g. to "adapt before adopting", by exporting a project and importing it with the support of a competence center (as I did in the past e.g. for tool-based management reporting / KPI / dashboard projects, as well for some organizational change activities)
Background of the concept:
a. in the late 1980s, worked for a software development unit of the consulting arm of an auditing firm, and we had aroud 5,000 people out of 70,000 focused just on collecting, processing, packaging, resharing information from projects, using an internal methodology to leverage on experience- I too was involved in developing a bit to be used specifically for Decision Support System model design
b. skipping other examples I worked on, saw, used in the past (1990-2000s), in the early 2000s used a tool that matched a similar approach, called Solonde, that was able to "read" into the SAP datamodel (thousands of tables, at the time) - enabling, indirectly, to recycle concepts (eventually Solonde I think was acquired by SAP, as more recent offers from SAP to access data actually used a similar approach)
