Create Sub-Task on transition

I did all of the above and tried it out.  No sub-task was created.  Do I have to tailor the JAVA source in some way and rebuild the JAR.

If no one objects, I would like to move this plugin into the Plugin Library.

I've adapted this code for the latest Jira release, and am having a massive problem.  It appears that this plugin will not work on the Create Issue transition.  I'm able to get a handle to the issue as an Issue, and create the new subtask from the fields, but when I try to call subTaskManager.createSubTaskIssueLink(), I'm having problems.  Specifically, it appears that because I'm in the Create Issue transition, issue.getGenericValue() is returning null on the original issue, which means while I can create the SubTasks, I cannot create the SubTask link.  Does anyone have any idea how I can go about doing this?

The instructions must be missing a step somewhere, as I get the same result as Norman.  The screen to add it to the workflow transition is there, but once the workflow is in place, it doesn't do anything.  No sub-task creation.

Thanks for sharing this plugins.

To make it workable in JIRA3.5.x, I did some midifications.

In the CreateSubIssueFunction.java,

GenericValue issue = (GenericValue) transientVars.get("issue");

--> Issue subIssue = (Issue) transientVars.get("issue");

Also you need to add a IssueImpl into the fields. Add myIssue.setProject(subIssue.getProject());.....and so on.

The API document of SimpleWorkflowManager.java is not correct because the "fields" parameter createIssue method only need issue(projectId and other keys are not necessary).

 Finally, it can work.

I followed all the instructions, but i do not see this plugin under Jira plugins when I go in Jira Adminstration. I also do not see the post function available. I'm using Jira 3.5, any idea abut what I need to do to get it to work

I have tried this on Jira 3.6 but it won't appear under Jira plugins.

Can somebody help me?

Do I need to do something to jar file?
I followed the instructions and put the jar file in the lib folder, restarted JIRA but it won't appear to plugins in Jira Administration.
This is first time I install plugin. What I might have done wrong?

Hi,

Will this plugin work in Jira 3.6? I added it, but no sub-tasks were created in the transition.

Do I need to do something to the plugin?
Is that 1.1 version of this plugin correct?

I had post functions before the issue creation. Now it works! Thanx, great plugin.

Need ideas on two issues:

1. I want to prevent the function from creating a subtask if it already created one. My workflows can, on occasion, re-run a step and I don't want to create the subtask the second time through.

2. I need another idea for the "create loop" because I want subtasks to be able to spawn siblings.

I followed the instructions for installation and configured a post function in my workflow. but i get the following error in my log file -

2006-09-05 03:05:33,974 ERROR \[atlassian.jira.workflow.SimpleWorkflowManager\] Error occurred while creating issue.
\[InvalidInputException: \[Error map: \[{}\]\] \[Error list: \[\[User 'null' doesn't have the 'Create Issue' permission\]\]\]

A nice feature would be use information from the "parent" issue in the name of the sub-task. For example use the "Summary" from parent issue as part of the name for the sub-task. Something like:

Sub-task Overview: $parent.summary - Accounting

When creating similar sub-tasks for different issues, this would automate the naming of them.

This is a great plugin. I need to automatically create a sub-task and assign it to someone other than the options provided (Parent issue's reporter and Parent issues assignee). Is there any way to change the Sub-Task Assignee so that I can point it at a particular user?

 Thanks!

Hello all,

I'm trying to get this working with 3.7.

I managed but I had to change the last function in the code by adding two parameters, the first one and the last one:

    private MutableIssue newIssueInstance(Issue issue)
    {
        return new IssueImpl(issue, issueManager, projectManager, versionManager, issueSecurityLevelManager, constantsManager, subTaskManager, attachmentManager);
    }

 Of course the function call must be changed too:

     MutableIssue subTaskIssue = newIssueInstance(issue);

And the attachmentManager must be added to the definitions:

     private final AttachmentManager attachmentManager = ManagerFactory.getAttachmentManager();

 Not to mention the imports:

 import com.atlassian.jira.issue.AttachmentManager;

 With these small modifications the plugin compiled with the jira-development-kit-3.7-beta2 and was able to run with Jira 3.7 and actually to produce a subtask on a wf transition.

Cheers!

Bettina 

Hello,

since there were some requests, I attached my .jar with the update for 3.7.

I had to rebuild it but could not test it, so please test it yourself.

Cheers

Bettina 

Hello,

I described the changes i made to the source code in my posting on the 21st of december 2006 above.

I think this is enough detail if you are working on the source.

For those who are not developing and just need the .jar, I uploaded mine to the attachments of this page.

I'm not going to upload my complete package as source code, because I have no intention to kidnap this package, neither to support it. Please ask the authors.

Cheers

Bettina 

This plugin, which was working wonderfully in v3.6.5 doesn't seem to work in v3.8.  Any assistance or comments are very much appreciated.  Thanks.

Just uploaded an updated version for Jira 3.8.

Hi, Paul:

I used this plagin a while ago, when I worked with Jira3.6, now I have Jira 3.8, so I  download your attachment to my C:\Program Files\JIRA-Enterprise-3.8.1\atlassian-jira\WEB-INF\lib dir, followed all your instructions and I don't see "Create subtasks on transition" among Postfunctions.

Any ideas?

Thanks, Irina 

No, I don't see any Errors, I'm thinking of upgrading to 3.9, would it work?

Thank you, Irina

Hello!

Thanks for the plugin for the version 3.8 ! I am trying to customise it ( assign to other than parent or reporter) and i would like to have the source code.

Is that possible? Could you attach it?

Thanks! 

Yes, the source code for the 3.8 would be nice

I have this excellent plugin working on 3.9.1; can i get the source code. Need to modify it little to add the parent's summary in the subtaks created with some modification.

thanks

Some additions (check and bug fix) in version 1.2 for JIRA 3.8 and above required:
- check for parent issue is subtask (or subtask with same workflow for detect recursive creating if multi level subtasks "hacked")
- very required add link to parent issue on creating like this: issueObject.setParentId(parentIssue.getId());
I modify code for 3.10 and add setParentId, because some my custom functions in create subtask workflow not working without parent Issue (copy some fields from parent Issue), but waiting "official" version with bug fix

Hi...

 I'm tasked by my company to set up Jira... I'm no developer... and new to Jira...

I was wondering if a similar plug-in exist... instead of creating a sub-task, it will create a separate issue on another project? and if this is possible with Jira...

appreciate your soonest reply....

thanks in advance...

Perhaps Im just not thinking "outside of the box" here, but how can one use this plug-in to ensure a sub-task is only automatically created just once per issue?

For example, I want a "Documentation" Sub-task to be automatically created when an issue is moved from "In Development" to "In QA".  If a QA resource finds issues during the QA process, they would move it back to "In Dev".   The problem is when a developer moves it back to QA again, another Doc Sub task will be created.

Thanks in advance!

Was anyone able to obtain the source code for the latest plugin? If not, can someone from the authors attach it?

thanks a lot.

Does this plugin work with 3.10?

Thanks. 

We had some issues with mail sending due to changes in mail templates.

I have attached my compilation with source.

Classpath jars:

osworkflow-2.8.0.jar;

ofbcore-entity-2.1.1-atlassian-2007-05-07.jar;

commons-lang-2.1.jar;

velocity-1.4.jar;

propertyset-1.3.jar;

osuser-1.0-dev-log4j-1.4jdk-7Dec05.jar;

log4j-1.2.7.jar

jira-createsubtask-postfunction-plugin-jira310-with-source.jar 

 This one works with 3.10.2.

Is anyone else seeing issues with Indexing?  My Subtasks are being created fine, but are not being indexed (evident when searching) until some other action occurs on the subtask.

Has anyone solved the recreating of subtasks issue?  Does this work on 3.11?  Thanks!

All,

     Please find the attached updated.jar file for 3.11 version which has the following functionality

1: Inherit Parent's priority to the Subtask

2: You can add Parents Summary + Key Id in the subtask Summary to relate the subtasks with Parent, eg. If I a do create an analyze sub task for my parent task i can put it as Analyze%.Key%.summary% so when the sub task is generated it will be Analyze -TEST-1201-This is a test main task.

I would give credit to Samuel John who made the customization. 

Hi,

I'm trying to get this plugin up and running (Enterprise Edition, Version: 3.11-#288) and after copying it to the lib directory and restarting JIRA it is not available under plugins in the admin.

Also, there wasn't anything in the logs

Any ideas? Thanks in advance.

I am getting such an error in jira.

2008-01-10 14:09:58,649 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There were problems loading the module 'workflow-function'. The module and its plugin have been disabled.
2008-01-10 14:09:58,654 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There was a problem loading the descriptor for module 'workflow-function' in plugin 'Metro Plugins'.
 Error retrieving dependency of class: com.telenor.jira.plugin.workflow.email.SendMailFunctionPluginFactory. Missing class: com/atlassian/jira/plugin/workflow/WorkflowPluginFunctionFactory
com.atlassian.plugin.PluginParseException: Error retrieving dependency of class: com.telenor.jira.plugin.workflow.email.SendMailFunctionPluginFactory. Missing class: com/atlassian/jira/plugin/workflow/WorkflowPluginFunctionFactory
        at com.atlassian.plugin.descriptors.AbstractModuleDescriptor.init(AbstractModuleDescriptor.java:69)
        at com.atlassian.jira.plugin.JiraResourcedModuleDescriptor.init(JiraResourcedModuleDescriptor.java:45)
        at com.atlassian.jira.plugin.workflow.AbstractWorkflowModuleDescriptor.init(AbstractWorkflowModuleDescriptor.java:29)
        at com.atlassian.jira.plugin.workflow.WorkflowFunctionModuleDescriptor.init(WorkflowFunctionModuleDescriptor.java:34)
        at com.atlassian.plugin.parsers.XmlDescriptorParser.createModuleDescriptor(XmlDescriptorParser.java:147)
        at com.atlassian.plugin.parsers.XmlDescriptorParser.configurePlugin(XmlDescriptorParser.java:85)
        at com.atlassian.plugin.loaders.SinglePluginLoader.loadPlugin(SinglePluginLoader.java:86)
        at com.atlassian.plugin.loaders.SinglePluginLoader.loadAllPlugins(SinglePluginLoader.java:50)
        at com.atlassian.plugin.loaders.ClassPathPluginLoader.loadClassPathPlugins(ClassPathPluginLoader.java:50)
        at com.atlassian.plugin.loaders.ClassPathPluginLoader.loadAllPlugins(ClassPathPluginLoader.java:63)
        at com.atlassian.plugin.DefaultPluginManager.init(DefaultPluginManager.java:70)
        at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:28)
        at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:356)
        at com.atlassian.jira.ComponentManager.start(ComponentManager.java:334)
        at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:31)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
        at org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
2008-01-10 14:09:58,661 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There were errors loading the plugin 'Metro Plugins'. The plugin has been disabled.
2008-01-10 14:10:05,429 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not find any custom field value with key 'com.atlassian.jira.ext.charting:firstresponsedate'.
2008-01-10 14:10:05,430 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not find any custom field value with key 'com.atlassian.jira.ext.charting:resolutiondate'.
2008-01-10 14:10:05,430 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not find any custom field value with key 'com.atlassian.jira.ext.charting:timeinstatus'.
2008-01-10 14:10:05,446 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not find any custom field value with key 'com.atlassian.jira.plugin.labels:labels'.
2008-01-10 14:10:05,524 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not find any custom field value with key 'com.atlassian.jira.toolkit:resolveddate'.
2008-01-10 14:10:06,794 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Enterprise Edition, Version: 3.11-#288
2008-01-10 14:10:06,794 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Configured to use database: mysql
2008-01-10 14:10:06,955 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl]

Hi

Could you upload the source code of version 1.2.1?

There is a necessity to use this useful plugin on initial transition "Create Issue". But it would be strange to use "Create Sub-task" postfunction
before "Creates the issue originally.", If we move down "Create Sub-task" postfunction. It without exception will be create sub-tasks till the StackOverflowException
will be thrown by in-memory hsql db (for my PC quantity of created sub-tasks is about 500+). With other not initial transition the plugin work fine.  
 
For now I work with Jira 3.12.1, but with Jira 3.9.1 have the same problem.
 
I need your advice on question "How I can fix it?" or it would be great if you fix it yourself. Thanks.
 

Can I use i18n properties within the field.subIssueOverview and field.subIssueDescription?

I am using 3.12.1.#299 and after trying to create sub-task with this plugin, is there the following error here

ERROR

It seems that you have tried to perform an illegal workflow operation.

If you think this message is wrong, please consult your administrators about getting the necessary permissions.

Form Errors:

Any advice, thanks

Dalibor (I have administrator rights)

This plug-in is terrific.  It has saved me a LOT of time.  One issue, though:

When I create an issue directly in JIRA my subtasks are created flawlessly.

When I create an issue via eMail (using the pop listener) - the parent issue is created but the subs are not.

 Anyone else see this behavior?

Does v1.2.1 work with JIRA 3.12.2?    

Hi,

 to get the "Send Notification Mail"-Plugin working i had to change the file  atlassian-plugin.xml in the jar. I had to change these to lines

 <resource type="velocity" name="view" location="sendmail-function-view.vm"/>
<resource type="velocity" name="input-parameters" location="sendmail-function-input-params.vm"/>

to 

<resource type="velocity" name="view" location="templates/sendmail-function-view.vm"/>
<resource type="velocity" name="input-parameters" location="templates/sendmail-function-input-params.vm"/>

Regards

Hartje

I see several people mentioned errors with version 1.2.1 of the plugin, and I think I've figured out why:

I was previously using version 1.2 of the plugin, which did not allow the priority of the sub-task to be configured.  But version 1.2.1 of the plugin does, so if you have workflows which used 1.2 and upgrade to 1.2.1, the error occurs when you make the transition because it can't find the priority which is configured when the subtask is created or edited.  I was able to just edit the subtask in my workflow and it seemed to fix the problem.  You could also modify the XML of the workflow directly to add the "<arg name="field.subIssuePriorityId">0arg> " line.
 

I ended up just reverting to version 1.2 so I wouldn't have to change a bunch of workflows, and 1.2 seems to work with JIRA 3.12.3.

Here is the XML from my workflow which used 1.2 of this plugin:

<function type="class">

  <arg name="field.subIssueAssignTo">1arg>
  <arg name="class.name">com.telenor.jira.plugin.workflow.createsubissue.CreateSubIssueFunctionarg>
  <arg name="field.subIssueOverview">Create Errata Reportarg>
  <arg name="field.subIssueTypeId">9arg>
  <arg name="field.subIssueDescription">If the issue is customer-visible, update the Errata Report document to describe the customer-visible impact of the issue. arg>
  function> 

And here is the XML from my workflow after I simply edited the plugin configuration and saved the changes:

<function type="class">   <arg name="field.subIssueAssignTo">1arg>
  <arg name="class.name">com.telenor.jira.plugin.workflow.createsubissue.CreateSubIssueFunctionarg>
  <arg name="field.subIssueOverview">Create Errata Reportarg>
  <arg name="field.subIssuePriorityId">0arg>
  <arg name="field.subIssueTypeId">9arg>
  <arg name="field.subIssueDescription">If the issue is customer-visible, update the Errata Report document to describe the customer-visible impact of the issue. arg>
  function>

Is there a xml based way of forcing the sub-task to be assigned to a specifc user instead of parent reporter or assignee?  Had a look the code but its a bit beyond me.  Would be nice if a transition could a bunch of sub tasks for specific users.

Which i then could use to block the next transition unless they are all closed (as a multiple review type situation) 

When creating sub-tasks they are created by the "null" user.  The reporter for the sub-tasks appear correctly once the tickets are created however my transition does not work unless anyone can create tickets in the project.

 Does anyone have a way around this?

i get the following error during performing the transition, where the create-subtask on transition post-function is implemented:

ERROR
It seems that you have tried to perform an illegal workflow operation.

If you think this message is wrong, please consult your administrators about getting the necessary permissions.

Form Errors:

Logfile output:

2008-07-01 21:46:44,569 TP-Processor16 ERROR [atlassian.jira.workflow.SimpleWorkflowManager] An exception occurred
java.lang.NullPointerException
at com.atlassian.jira.workflow.SimpleWorkflowManager.createIssue(SimpleWorkflowManager.java:165)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:365)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:313)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:71)
at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
at $Proxy21.createIssue(Unknown Source)

Any idea what is wrong?

Great Plugin Amit and Sam..   I will definately use it and share my comments

Has anyone tried to compile the source code lately.?  I downloaded it from the link above and grabbed all the jars listed in the .classpath file except the kk.jar which I couldn't find.  Still Eclipse can't resolve numerous imports etc...  I'm new on the plugin development side so I may be missing something.  Thanks for your help!!!

Amit/Sam,

1. How any Sub-Task can be added.! Is their any limit to it.?

2. In my JiRA I have disabled issues to be unassigneed. But using this plugin Sub-task can be left Unassignee.  This should not be the case.

Getting following error after clicking on the Transaction link of the issue.:  (Note I am trying this on JiRA 3.12.3 );

I get an exception when I click on the Add button under the 'send email notification' post function.

 I am running Jira 3.12.1

and

create-subtask-on-transition-1.2.1.jar
 

(I already tried that thing above with changing the location in the xml file)

java.lang.IllegalArgumentException: Cannot find expected argument 'groupEmails' in parameters.
at com.atlassian.jira.plugin.workflow.AbstractWorkflowPluginFactory.extractSingleParam(AbstractWorkflowPluginFactory.java:116)
at com.telenor.jira.plugin.workflow.email.SendMailFunctionPluginFactory.getDescriptorParams(SendMailFunctionPluginFactory.java:42)
at com.atlassian.jira.web.action.admin.workflow.AddWorkflowTransitionFunctionParams.addWorkflowDescriptor(AddWorkflowTransitionFunctionParams.java:64)
at com.atlassian.jira.web.action.admin.workflow.AbstractAddWorkflowTransitionDescriptorParams.doExecute(AbstractAddWorkflowTransitionDescriptorParams.java:67)
at webwork.action.ActionSupport.execute(ActionSupport.java:153)
etc......

Edit:  Solved!! I had two create subtask jar files with the same filename, but they were downloaded at different times and had different file sizes. I copied over the smaller/older one with the newer one, and this post function now works.

At first: Thanks for this plugin!

As I've seen there some comments regarding the request of issue creation instead of sub-tasks. Because I need such a functionality too, I asked Atlassian support. The answer was: Not available, create your own plugin.
Becasue there's no knowledge about JIRA plugin development on my side, I wanted to ask if it is possible to get support from you or if someone already has developed a customized version based on this plugin.

Michael

The send email notification post function does not seem to deal with issues or sub-tasks that are unassigned.

 2008-09-08 11:43:27,635 TP-Processor1 ERROR [web.action.issue.CreateSubTaskIssueDetails] com.atlassian.jira.exception.CreateException: com.atlassian.jira.workflow.WorkflowException: com.opensymphony.workflow.WorkflowException: Failed to send email: root cause: No user null found
com.atlassian.jira.exception.CreateException: com.atlassian.jira.workflow.WorkflowException: com.opensymphony.workflow.WorkflowException: Failed to send email: root cause: No user null found

It automatically wants to send it to  these people:

A notification email will be sent to the Issue Assignee, the Issue Reporter, the "foobar" group members

I only want it to go to the group, becuase the "Issue Assignee" is unassigned causing this error.

Thanks for this plug-in, I use it a lot.

One problem I am having is that the sub-task is created without a security level assigned.  Even if I set security level as a required field for the sub-task issue type, the post-function is able to create sub-tasks with no security level assigned.  Ideally, the sub-tasks would inherit the parent issue security level.  Is that possible?

This functionality is not implemented in this plugin. If you want you can add the same and update the code and please check in the new code + comments etc here.

Thanks

Amit

Helllo, is posible to add custom fields in the create/edit templates (createsubissue-function-edit-params.vm and createsubissue-function-input-params.vm)when I had the sub-tasks?

Thx

This plug in is helpful. 

1. How do I make it so that the sub task inherits the parent name + some text?

2. How do I make it so that I can specify the fix in version for the sub-task?

Ultimately I wish that sub tasks were automatically created when an issue needed to be fixed in multiple versions.  So I am creating a transition called "Merge bug fix to 3.1 release" and one called "Merge bug fix to 3.2 release", etc and then the project manager can click on the workflow step to create these automatically.  This makes it easier than creating all the sub tasks manually.  If I can assign the fix in version field automatically in this post function then this seems like a workable work around.

Thanks for your help!

Hi,

could you please provide a plugin compiled for the JVM 1.4? The plugin reports the following error:

Error:There was a problem loading the descriptor for module 'workflow-function' in plugin 'Metro Plugins'. Class version is incompatible with current JVM: com.telenor.jira.plugin.workflow.email.SendMailFunctionPluginFactory

Thanks for the great plugin,

Aki

Will this plugin work for Jira 3.13?

I am testing the plugin in v3.13.  I am encountering an error.  I have the workflow set up to assign the issue to the parent issue's assignee, but instead it keeps assigning it to the lead developer.  I checked the log and the here is what it says:

2009-03-02 13:16:48,629 http-8080-Processor25 WARN [workflow.function.issue.AssignToLeadFunction] Automatically setting assignee to lead developer.

It seems as if there is a problem to me. Is this because the plugin doesn;t work with 3.13?

Great plugin, very useful, however I'd like to try and modify it to copy the following fields from the parent

• JIRA fields - Affects Version/s and Fix Version/s
• Custom fields

Being a complete novice with Java, I've got an idea of the source code, and think this should be a fairly trivial change; however I'm not 100% confident on what I should be changing. Iif someone could give some pointers on what parts of the code I need to modify to do this I'd be very grateful.

I am using it within JIRA 3.13 and it works fine.

I am testing out JIRA 3.13.2  and after I installed the 'create-subtask-on-transition-1.2.1.jar' file I went into the Admin Current Plugins screen and found this error under the Metro Plugins:

Metro Plugins

Description: Plugins for supporting the Metro roadmap process
Vendor: [Paul Rene Jørgensen

What did I do wrong, or what do I need to do to fix this?