Alexey Matveev Expert

Hello, You install your plugin on any instance you like or redirected by Load balancer. After it your plugin will be available on all instances

Try to find Stuck status in cog item->issues->statuses

here is the article https://confluence.atlassian.com/adminjiraserver071/configuring-workflow-schemes-802592719.html Do not give up. It can be a bit complicated in the beginning.

Kindly read the following article https://confluence.atlassian.com/adminjiraserver071/auditing-in-jira-applications-802593030.html

Hello, Status can not be deleted if there are issues associated with the status. I think sombody renamed it. 

 Hello, Your team logs hours because it uses the Log work button. If you want your team to log story points then disable time tracking and add story points field to all issue types.If you follow the guide below you will disable time tracking for the whole instance.…

That is all. make comand atlas-mvn clean install

change your atlassian-plugin.xml <?xml version="1.0" encoding="UTF-8"?> <atlassian-plugin key="${project.groupId}.${project.artifactId}" name="${project.name}" plugins-version="2"> <plugin-info> <description>${project.description}</description> <version>${project.version}</version> <vendor…

First of all, you change your pom like this. It will be installed without these changes but you can have problems during later usage of your plugin <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"…

Use Jquery to do what you want to do. But I would not advise you to do it. Too much hassle and possible problems.

It should work. Put there a simple javascript which will return alert to you and check. <span><script></span><span> alert( 'Hello, world!' ); </span><span></script></span>

Hello, Do you mean that you put javascript into the description of the field? Your jira version is not Cloud?

Hello, You need to have delete issues permission for deleting an issue in a project. You can read about permission schemes here https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

Can you compile your code. You have wrong parenthis closing. Your code should be like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.CustomFieldManager import com.atlassian.jira.issue.Issue CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager();…

Hmmm. I can not find JsIncluder. I just asked in the russian user group what happened to the plugin.

Jsincluder will let you store your JavaScript and link it to create, edit, view, transition screens. But all logic you have to develop yourself. There is JQuery available, that is why if you want to hide an element it would be like this AJS.$("elementselector").hide() You can hide not only elements buy whole divs. The…

You can use Jsincluder plugin to add your Javascript there. If it is Cloud, then it is impossible

Hello, Javascript. But it s an ugly solution. Difficult to mantain.

<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.example.plugins.tutorial</groupId>…

I took the code from here https://bitbucket.org/atlassian/tutorial-jira-simple-issue-crud/downloads/ With modification to pom.xml I packaged it for Jira 6.4.5. You can not package it for Jira 7 because of the api used in the code. You would need to change it too.

It is a bit time consuming to follow the tutorial. If you had your code in github or bitbucket, it would be easier to have a look at your problems. 

There are some restrictions on workflow editing. Copy the workflow. Make all changes to the copied workflow and then associate it with the project workflow scheme. Read here about workflow limitations https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html I guess you limitation is * If a…

What operation are you trying to do? Could attach a screenshot

In the atlassian-plugin.xml add <context>jira.general</context> for your resources. See if it works. If it works, then you can find the necessary contex later

It is written in the article why it is recommended. If these conditions are true for you, then use the native backup. after you change your workflows you will need to publish them. If you deleted statuses then Jira will ask you to move issues which are in the deleted statuses to the new ones. After it the change will be…

Hello, Put in your velocity template for the custom field the following code to the first line $webResourceManager.requireResourcesForContext(argument) as argument provide reference to your resource defined in altassian-plugin.xml

I see, Go back to the workflow and create transitions between statuses. For example, you would need to create a transition from "to do" status to the new status. You can read more here https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html Go to Workflow designer part

Hello, You can define a user property for each user which would identify the user. You can read more about user properties here: https://confluence.atlassian.com/adminjiraserver073/create-edit-or-remove-a-user-861253174.html Go to Add a property to a user part

You can publish it. Where you can not see statuses? After you created an issue, then view the workflow for the issue. Can you see your new statuses? Or you can not see your statuses on the board?

Yes, that is what I mean. You want to backup your system in case somehting happens in the production after you made change in the production workflows, right? You can read about Jira backup here https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html