Charlie Gutjahr (Inactive) added a comment - 26/Jun/2023 8:05 AM ProForma 8.8.0 has now been released which is compatible with Jira 9.8.0 and later.

Charlie Gutjahr (Inactive) added a comment - 26/Jun/2023 7:56 AM We have released ProForma 8.8.0 today which makes ProForma compatible with the latest versions of Jira. This includes Jira 9.8 & 9.9 as well as Jira Service Management 5.8 & 5.9. Jira 9.8.0 changed which libraries are provided for XML processing which made it difficult for ProForma to implement a single version which works both before and after Jira 9.8.0. So for now we have a minimum requirement of Jira 9.8.0 on ProForma 8.8.0; for older versions of Jira please continue to use ProForma 8.7.0. Both versions provide the same functionality. I expect future releases of ProForma to return to supporting Jira 8.0.0+ again, hopefully with one ProForma release that works on all Jira versions but if that proves not possible we can publish two versions to cover the full range.

Penny Ecaruan added a comment - 22/Jun/2023 4:49 PM - edited a

Penny Ecaruan added a comment - 22/Jun/2023 4:47 PM We'd really like to be able to upgrade our Jira instance so that we can keep up to date, but are unable to because of THIS issue.  First, to have the issue type be a "Suggestion" is way off course.  THIS IS A BUG that needs to be addressed.  This Add-On is a PAID for add-on that is causing issues.  Atlassian bought out ProForma (which was VERY quick at resolving issues in the past) and now it's terrible. I'd at least like an update on this and to see it changed from a "Suggestion" to the "Bug" that it truly is.

Ilia Shapira added a comment - 14/Jun/2023 4:59 PM We been using Jira for many years. Unfortunately it seems like a trend. Especially with Data Center / Server. Someone creates a good plugin. A few years later Atlassian decide to buy it and then the support and feature development goes down the drain.  This issue creates a huge pain in the ....  for us and it would be nice at least to hear something from Atlassian and for sure not to label it as suggestion. I understand that they are not always able to keep up with all the plugins and all the updates, but two months....

jira.admins@biamp.com added a comment - 14/Jun/2023 4:36 PM ... 44 days , and counting , with no solution, only a workaround which was offered by another customer. Silence from Atlassian, who now owns ProForma? AND Jira 9.9 breaks the workaround...?

jira.admins@biamp.com added a comment - 14/Jun/2023 2:39 PM This has been going on far too long.  We have PAID for a product that we cannot use if we upgrade to the latest version of Jira.  The work around that is listed doesn't work with 9.9 so now, not only are we unable to use an add-on that we PAID for, we are unable to keep current on the Jira upgrades. This is not acceptable at all.  This should not be a "SUGGESTION" as an issue type, it should be a blocking "BUG".

Ilia Shapira added a comment - 13/Jun/2023 4:17 PM Yes I tried 9.9.0 same problem Workaround also doesn't work 

Andreas H added a comment - 13/Jun/2023 4:05 PM - edited It seems that proforma development is very slow. Looking at versions table we can see that it can take up to 8 months for a new version.  It is a pity because new Jira version 9.9 is already there and not even a compatible Proforma version for Jira V 9.8x is available.   Has someone already tested Jira 9.9 with Proforma plugin V 8.7.0 - same behavior?  

Ilia Shapira added a comment - 13/Jun/2023 3:09 PM Its already Jun 13 and still no update ?!

Maria Salazar added a comment - 07/Jun/2023 6:00 PM Workaround gave us the ability to enable the plugin but no other configs are available still.

derek.a.boonchaisri.civ@us.navy.mil added a comment - 26/May/2023 4:58 PM GOAT! Thank you Konrad!

Andreas H added a comment - 26/May/2023 11:23 AM Hello Konrad, your suggestion helps! With 7-Zip (e.g.) the jar file in installed-plugin-folder can be opened and manifest.mf can be changed and saved directly. After activating plugin again everything works.  Thanks a lot! Best regards  

Konrad Garus added a comment - 26/May/2023 8:49 AM If you're desperate, it's actually fairly easy to work around. Unzip the proforma JAR, edit META-INF/MANIFEST.MF and remove the following from Import-Package: org.apache.xml.dtm,org.apache.xml.dtm.ref Or use the MANIFEST.MF below. Then zip everything back and install this updated JAR via UPM. (Use at your own risk. I am just another customer/consultant/developer, not affiliated with Atlassian or ProForma.) Updated contents of MANIFEST.MF: Manifest-Version: 1.0 Bundle-Description: ProForma Forms and Templates plugin for Jira Serve  r, by ThinkTilt. Bundle-SymbolicName: com.thinktilt.proforma.add-on Built-By: root Bnd-LastModified: 1681873689241 Bundle-ManifestVersion: 2 Bundle-DocURL: https: //www.thinktilt.com/ Bundle-Vendor: ThinkTilt Import-Package: com.atlassian.servicedesk.api.automation.configuration  .ruleset;resolution:=optional,com.atlassian.servicedesk.api.automatio  n.execution.message;resolution:=optional,com.atlassian.servicedesk.sp  i.automation.rulethen;resolution:=optional,com.atlassian.pocketknife.  api.commons.error;resolution:=optional,com.atlassian.servicedesk.api;  resolution:=optional,com.atlassian.servicedesk.api.approval;resolutio  n:=optional,com.atlassian.servicedesk.api.customer;resolution:=option  al,com.atlassian.servicedesk.api.field;resolution:=optional,com.atlas  sian.servicedesk.api.info;resolution:=optional,com.atlassian.serviced  esk.api.permission;resolution:=optional,com.atlassian.servicedesk.api  .portal;resolution:=optional,com.atlassian.servicedesk.api.request;re  solution:=optional,com.atlassian.servicedesk.api.requesttype;resoluti  on:=optional,com.atlassian.servicedesk.api.util.paging;resolution:=op  tional,com.atlassian.servicedesk.plugins.automation.api.configuration  .ruleset;resolution:=optional,com.atlassian.servicedesk.plugins.autom  ation.api.execution.error;resolution:=optional,com.atlassian.serviced  esk.plugins.automation.api.execution.message;resolution:=optional,com  .atlassian.servicedesk.plugins.automation.spi.rulethen;resolution:=op  tional,com.codebarrel.automation.api.thirdparty;resolution:=optional,  com.codebarrel.automation.api.thirdparty.audit;resolution:=optional,c  om.codebarrel.automation.api.thirdparty.context;resolution:=optional,  com.codebarrel.automation.api.thirdparty.context.result;resolution:=o  ptional,com.atlassian.cache,com.atlassian.core.util,com.atlassian.eve  nt.api,com.atlassian.jira.avatar,com.atlassian.jira.application,com.a  tlassian.jira.bc,com.atlassian.jira.bc.issue,com.atlassian.jira.bc.is  sue.fields,com.atlassian.jira.bc.issue.properties,com.atlassian.jira.  bc.issue.search,com.atlassian.jira.bc.project.component,com.atlassian  .jira.bc.project.property,com.atlassian.jira.bc.user.search,com.atlas  sian.jira.component,com.atlassian.jira.config,com.atlassian.jira.conf  ig.util,com.atlassian.jira.datetime,com.atlassian.jira.entity.propert  y,com.atlassian.jira.event.issue,com.atlassian.jira.event.type,com.at  lassian.jira.exception,com.atlassian.jira.issue,com.atlassian.jira.is  sue.attachment,com.atlassian.jira.issue.changehistory,com.atlassian.j  ira.issue.comments,com.atlassian.jira.issue.context,com.atlassian.jir  a.issue.customfields,com.atlassian.jira.issue.customfields.manager,co  m.atlassian.jira.issue.customfields.option,com.atlassian.jira.issue.f  ields,com.atlassian.jira.issue.fields.config,com.atlassian.jira.issue  .fields.config.manager,com.atlassian.jira.issue.fields.layout.column,  com.atlassian.jira.issue.fields.layout.field,com.atlassian.jira.issue  .fields. rest ,com.atlassian.jira.issue.fields. rest .json,com.atlassian.  jira.issue.history,com.atlassian.jira.issue.issuetype,com.atlassian.j  ira.issue.priority,com.atlassian.jira.issue.resolution,com.atlassian.  jira.issue.search,com.atlassian.jira.issue.status,com.atlassian.jira.  issue.status.category,com.atlassian.jira.jql.builder,com.atlassian.ji  ra.jql.parser,com.atlassian.jira.license,com.atlassian.jira.permissio  n,com.atlassian.jira.plugin.searchrequestview,com.atlassian.jira.plug  in.webfragment.conditions,com.atlassian.jira.plugin.webfragment.conte  xtproviders,com.atlassian.jira.plugin.webfragment.model,com.atlassian  .jira.plugin.workflow,com.atlassian.jira.project,com.atlassian.jira.p  roject.type,com.atlassian.jira.project.version,com.atlassian.jira.sec  urity,com.atlassian.jira.security.plugin,com.atlassian.jira.security.  roles,com.atlassian.jira.user,com.atlassian.jira.user.util,com.atlass  ian.jira.util,com.atlassian.jira.util.collect,com.atlassian.jira.util  .thread,com.atlassian.jira.web.bean,com.atlassian.jira.workflow,com.a  tlassian.plugin,com.atlassian.plugin.event.events,com.atlassian.plugi  n.web,com.atlassian.plugins. rest .common.security,com.atlassian.plugin  s.whitelist,com.atlassian.query,com.atlassian.query. operator ,com.atla  ssian.query.order,com.atlassian.sal.api,com.atlassian.sal.api.auth,co  m.atlassian.sal.api.pluginsettings,com.atlassian.sal.api.transaction,  com.atlassian.sal.api.user,com.atlassian.templaterenderer,com.atlassi  an.upm.api.license,com.atlassian.upm.api.license.entity,com.atlassian  .upm.api.util,com.atlassian.webresource.api,com.atlassian.webresource  .api.assembler,com.google.common.base,com.google.common.collect,com.o  pensymphony.module.propertyset,com.opensymphony.workflow,com.opensymp  hony.workflow.loader,com.riadalabs.jira.plugins.insight.channel.exter  nal.api.facade;resolution:=optional,com.riadalabs.jira.plugins.insigh  t.services.model;resolution:=optional,javax.annotation,javax.crypto,j  avax.crypto.spec,javax.imageio,javax.inject,javax.naming,javax.net.ss  l,javax.security.auth,javax.security.cert,javax.servlet,javax.servlet  .http,javax.ws.rs,javax.ws.rs.core,javax.xml.bind.annotation,org.apac  he.commons.io,org.apache.commons.io.output,org.apache.commons.lang,or  g.apache.commons.lang3,org.apache.commons.lang3.builder,org.apache.lo  g4j,org.bouncycastle.jce.provider,org.codehaus.jackson.map,org.slf4j,  org.springframework.beans.factory,org.springframework.beans.factory.a  nnotation,org.springframework.beans.factory.config,org.springframewor  k.context,org.springframework.context.annotation,org.springframework.  stereotype,com.atlassian.servicedesk.api.automation.configuration.rul  eset.validation;resolution:=optional,com.atlassian.servicedesk.api.au  tomation.execution.message.helper;resolution:=optional,com.atlassian.  servicedesk.spi.automation.visualiser;resolution:=optional,org.spring  framework.osgi.context;resolution:=optional,org.springframework.osgi.  service.exporter.support;resolution:=optional,org.springframework.osg  i.service.importer.support;resolution:=optional,org.eclipse.gemini.bl  ueprint.context;resolution:=optional,org.eclipse.gemini.blueprint.ser  vice.exporter;resolution:=optional,org.eclipse.gemini.blueprint.servi  ce.exporter.support;resolution:=optional,org.eclipse.gemini.blueprint  .service.importer.support;resolution:=optional,com.atlassian.migratio  n.app;resolution:=optional,com.atlassian.plugin.osgi.bridge.external,  org.osgi.util.tracker;resolution:=optional,org.osgi.framework.wiring,  com.atlassian.activeobjects.external,com.atlassian.extras.api,com.atl  assian.extras.api.jira,com.atlassian.fugue;resolution:=optional,com.a  tlassian.jira.bc.issuetype.property,com.atlassian.jira.bc.license,com  .atlassian.jira.bc.project,com.atlassian.jira.config.properties,com.a  tlassian.jira.entity,com.atlassian.jira.event,com.atlassian.jira.issu  e.fields.layout,com.atlassian.jira.issue.fields.screen,com.atlassian.  jira.issue.label,com.atlassian.jira.issue.link,com.atlassian.jira.iss  ue.operation,com.atlassian.jira.issue.views.util,com.atlassian.jira.p  lugin.license,com.atlassian.jira.plugin.webfragment,com.atlassian.jir  a.timezone,com.atlassian.jira.util.json,com.atlassian.jira.util.lang,  com.atlassian.jira.util.system,com.atlassian.plugin.event,com.atlassi  an.plugin.osgi.factory,com.atlassian.plugins. rest .common.multipart,co  m.atlassian.query.clause,com.atlassian.sal.api.lifecycle,com.atlassia  n.sal.api.message,com.atlassian.sal.api.upgrade,com.atlassian.schedul  er,com.atlassian.scheduler.config,com.atlassian.scheduler.status,com.  opensymphony.util,com.opensymphony.workflow.spi,com.sun.jersey.spi.co  ntainer,io.atlassian.fugue;resolution:=optional,javax.xml.datatype,ja  vax.xml.namespace,javax.xml.parsers,javax.xml.stream,javax.xml.stream  .events,javax.xml.stream.util,javax.xml.transform,javax.xml.transform  .dom,javax.xml.transform.sax,javax.xml.transform.stream,org.apache.co  mmons.codec.binary,org.apache.commons.logging,org.apache.lucene.searc  h,org.codehaus.jackson.annotate,org.joda.time,org.joda.time.format,or  g.ofbiz.core.entity,org.osgi.framework,org.springframework.aop,org.sp  ringframework.aop.support,org.springframework.beans,org.springframewo  rk.beans.factory.parsing,org.springframework.beans.factory.support,or  g.springframework.beans.factory.xml,org.springframework.core,org.spri  ngframework.core.io,org.springframework.util,org.w3c.dom,org.w3c.dom.  bootstrap,org.w3c.dom.ls,org.xml.sax,org.xml.sax.ext,org.xml.sax.help  ers Require-Capability: osgi.ee;filter:= "(&(osgi.ee=JavaSE)(version=1.8))" Atlassian-Plugin-Key: com.thinktilt.proforma.add-on DynamicImport-Package: com.botronsoft.cmj.spi.*;resolution:=optional,c  om.codebarrel.automation.api.thirdparty;resolution:=optional,com.code  barrel.automation.api.thirdparty.*;resolution:=optional,com.codebarre  l.automation.api.thirdparty.context.*;resolution:=optional,com.codeba  rrel.automation.api.thirdparty.context.result.*;resolution:=optional,  com.atlassian.migration.app Tool: Bnd-3.5.0.201709291849 Spring-Context: * Bundle-Name: ProForma: Forms for Jira Bundle-Version: 8.7.0 Atlassian-Build-Date: 2023-04-19T03:07:50+0000 Atlassian-Scan-Folders: META-INF/plugin-descriptors Created-By: Apache Maven Bundle Plugin Build-Jdk: 1.8.0_275

Andreas H added a comment - 25/May/2023 4:32 PM The Priority of this bug should be high not low!

Andreas H added a comment - 25/May/2023 4:31 PM This bug is a nightmare. We are waiting since 3 weeks for a proforma-plugin-upgate but nothing happend. Why does it takes so long to fix this know bug? Other plugin-providers are much faster solving such massive issues.

jira.admins@biamp.com added a comment - 25/May/2023 3:44 PM This is substantially impacting our company as we use the ProForma forms on a regular basis to submit work order tickets for our Hardware/Compliance and other teams.  This is very important to get resolved.