Derek Fields _RightStar_ Community Champion

It depends on how you are making the automated change. If you are using Automation for Jira or ScriptRunner, you can run the automation as a specific user, which will associate the change with that user. Other plugins may not let you set the user running the transition.

I find when I am looking at large numbers of issues, it is easier to download the query to Excel, where I can do whatever number crunching or further filtering that I want to do. If you use the Export function, you will get all 1555 rows in the CSV file.

Make sure that your code is in the Initialization and not in the field behavior. The initialization will set the default text when the screen is first displayed. After that, it won't run. If you put it into the field behavior script, it will run every time the field is updated. 

Creating such a script isn't that difficult, but it is fair amount of work. For me, it would take about 2-3 hours to write and test. Maybe someone else can do it faster.

Why not just use the "Create with Shared Confiuration" option in the Project Creation screen? That will copy all of the schemes associated with the template project to the new project. 

You should make this person a Jira Admin, not a Site Admin. Then he will be able to manage the Jira side without having that access level in Confluence.

This version works exactly as expected. Note that I am passing only the extra part of the endpoint into the "get" call. The way the get works is that is determines whether you are passing in the enter URL starting with http... or whether you are passing only the specific endpoint, which is concatenated to the server that…

I am not aware of any available RUP templates. You will have to create this for yourself.

There are several plugins that will support this. Automation for Jira is one that works outside of a Workflow to support this kind of automation. You can also build it within a workflow with one of the plugins such as JMWE or JWT. You cannot get this behavior without a plugin.

One semantic problem is that you appear to view Tasks as sub-components of Stories. In Jira, they are siblings. Many people use Sub-Tasks to record the specific action(s) to be done to move an Issue (a Story or Task) from open to closed. The way Sprints work in Jira is that all Sub-Tasks are expected to be completed for an…

Here is a simple Groovy REST-oriented class that I created to make it simple to make REST calls. Note the usage section at the bottom that shows how to turn the response into a Groovy object import groovy.json.JsonOutput import groovy.json.JsonSlurper import org.apache.commons.codec.binary.Base64 public class RestClient {…

Agree with @John Funk - to extend on the explanation, the order in which the issues are displayed is determined by the filter that is used to select the issues. You cannot have a different order for each column. I agree also that it is not clear what value there is in seeing the order in which issues were completed on the…

Post-functions fire in the order in which they are called. Issue A creates Issue B. The creation of issue B may create Issue C. It will happen in that order. I think your real question is the order of the reindexing? I am not sure, but it may be indeterminate. If the plugin that creates the new issue spawns a new thread to…

I am not familiar with RUP. The short answer is that you can model any workflow process that you want in Jira. While Jira Software focuses on Agile software development, of which Scrum and Kanban are two leading methodologies, any workflow that you can model can be implemented in Jira.

I reported it to them.

I tried it in my Cloud environment. It doesn't work correctly for me either. It appears that this is a bug that should be opened with Atlassian.

Try multiplying the timestamp by 1000 to change it from seconds to milliseconds. 

You don't specify whether you are on Cloud or Server. The APIs for each are different. I can see, though, from the documentation that you are using Cloud, which makes a different. In any case, try using: https://{host}/rest/api/2/issue/{issue_key}/worklog?startedAfter=1575932400 leave out the "jql=". That should return…

ScriptRunner has a builtin JQL function called LinkedIssuesOf that takes a subquery. This would let you write: issuetype="AI2 Order" and issueFunction in linkedIssuesOf("IssueType = \"Field - Test\"") and "Flight plan" ~ "No plan"

I am not familiar with the Workday REST API; assuming that it returns the values as a JSON document, then the general pseudo-code for doing this is straightforward; * Call the Workday REST API, retrieving the results as a JSON document * Convert the JSON document into a Groovy Object (usually a Map of some sort) Once you…

You could use Comments for the monthly status. Getting a report like this would require exporting the Issues (one per project) to Excel or Word or using a plugin to allow you to create a custom report. Another approach, which might be easier, is to make the monthly status a sub-task of the Issue. Each month, the project…

In my case, it was caused by the Brikit plugin (which literally "bricked" the space)

No, TLBLUE-100 will not be available for use. Jira doesn't reuse keys even if you move or delete the issue.

The only way to do this is to create a filter that contains all of the fields that you want to export. Conceptually, all fields are available to all projects to use, so there is no way for Jira to determine which fields are associated with a specific project. It is possible to use a field doesn't appear on a screen, so…

What makes this tricky is that Jira will only let you transition to a status that is explicitly permitted by the workflow. As I understand what you want, you want to be able to transition from Status A to Status B and have a generic "Resume" button that will take the user back to Status A. This is going to be a fair amount…

I suggest that you contact the vendor directly.

The short answer is that there is no API that will return the information that are trying to get. You can look at this post: https://community.atlassian.com/t5/Jira-Core-questions/How-to-obtain-ItemId-in-api-2-dashboard-dashboardId-items-itemId/qaq-p/189400. As you will see, there is no API that will return to you the…

Does this refer to a plugin? If so, you need to ask the vendor on their support site.

I am the practice manager for an Atlassian partner. If you want to talk about your issue - contact me at derek.fields@rightstar.com

Are you looking to populate custom fields? For instance, Requester already populates with the Jira user name for the requester, which has the email. You can use the requester to populate custom fields during issue creation utilizing post-functions. You will need a plugin to allow you to do that. You also need a source for…