Tarun Sapra Community Champion

1 ) Move the story to Epic. 2) Now, you have Epic with 20 sub-tasks, move the 20 sub-tasks using bulk udpate to "story" type. Before bulk moving sub-tasks make sure the "create" issue screen of the story type has the mandatory field "Epic Link" thus when moving the 20 sub-tasks you can fill the mandatory field "Epic Link"…

Here's the guide https://confluence.atlassian.com/jirakb/how-to-migrate-projects-from-one-jira-cloud-application-to-another-779160766.html But using the above instrcutions you will loose data on JIRA 2 as JIRA 2 will be populated with data from JIRA 1. Thus, you need to merge 2 JIRA cloud instances.…

"Is this going to filter all updates on the worklog between those days?" No, that's not the case. Because workLogDate basically means the "Date selected" while logging work - https://jira.atlassian.com/browse/JRASERVER-1959 This date can be in future as well. So the JQL which you have shared will only fetch issues which…

Hello Manfred, Is it correct, that the epics in JIRA are similar to the features in TFS? Yes, that's correct. Also, JIRA doesn't enforce anyhierarchy such that you can have subtasks for Epic which isn't ideal but you can have that. I have been part of TFS to JIRA migration. And the issuesType mappin is as follows TFS…

Hello Nitesh, For stacked bar charts I use the Dataplane Arsenale reporting plugin. Though the plugin xCharts as suggested by Nicolas also looks interesting, it's upto your use-case and pricing. Thus, you can install and start the evaluation of the reporting plugin of your choice.

Hello Maxwell, For the JQL function membersOf("<group-name>") autocomplete isn't supported. Thus, the user has to provide the name explicitly. 

Without using plugins you can't do this in JIRA. You need scripted fields from the script runner plugin. Some samples - https://scriptrunner.adaptavist.com/5.0.4/jira/scripted-fields.html At runtime when the screen loads you can calculate the linkedissues based on link type and show their count in the custom field.

If it works for you, then please accept/upvote the answer.

Done/Resolved issues are generally not editable until or unless you explicitly make them editable. https://confluence.atlassian.com/jira/allow-editing-of-closed-issues-138704.html ALso certain fields like created, resolved, updated are auto populated and can't be edited.

Sprint report won't reflect issue changes once the sprint is complete.

Since the assignee is not changing when the issue is resolved thus you can use something like (status changed FROM "In review" to "resolved") and assignee in membersOf("jira-developers") Here instead of "jira-developers" group you can use any group and make sure that group is in the "developer" role of the project. I…

Using components to display teams would like abusing the components. Generally how I do it at various clients is to have a custom field called "Teams" or "Squad" or whatever you want to call it. This custom field is of type "select drop-down" and it shows the list of names of various teams. Now, while creating the issue…

If it works for you then please upvote/accept the answer.

Hello Ina, "Updated" does cover any change to the issue. And Yes logging work/time on an issue is covered by the "updated"

If it works for you, please accept the answer. thanks.

From the docs "If an email message contains an issue key in its subject line and that issue key exists in your JIRA installation, the handler will add the email message content as a comment on the issue, regardless of which project the issue is in." Thus, make sure that the emails you receive have the issuekey in the…

Just make it Pattern.compile("^([0-9]{5,8})\$")

Hello, You can't convert an add-on meant for cloud into JIRA server. Because both provide different frameworks for development of add-ons. Cloud addons use "Atlassian connect" framework which is different from the framework Plugins2 used by the addons for JIRA server. Best way to check an addons availability is to check on…

Hello Armin, You don't need to edit any html page for this. JIRA already provides a text area which accepts content for the announcement banner. Please see here - https://confluence.atlassian.com/adminjiraserver071/configuring-an-announcement-banner-802592288.html 

You need to have listerner in place for the "Issue assigned" event, which is listening for changes on the assignee field. LIstener - https://confluence.atlassian.com/adminjiraserver071/listeners-802592235.html Script runner plugin also provdes ability to write listerner…

duedate < -30d and resolution is empty This will get you all unresolved issues which have dueDate before the last 30 days i.e 30 days post duedate 

Component is a generic term which can be used effectively to represent an module of an project. For example - When creating user stories in an large project the Product owner can choose the component like - UI, Database, Backend, API etc Thus, based on components it becomes easy to filter issues meant for specific…

If it works for you, then please accept/upvote the answer. Thanks.

Date compare isn't supported yet by JIRA . Open issue here - https://jira.atlassian.com/browse/JRASERVER-20727 But there are plugins available which provide additional JQL function. Like "Script Runner" plugin has plenty of JQL of functions and your requirements can easily be implemented by using the query issueFunction in…

Anna you were missing the dollar sign ($) in your snippet which means "don't add anything after me" as dollar sign means end of line.

Try this Pattern.compile("^([0-9]{8})$")

Please accept/upvote the answer if it solves your query. Thanks.

Please see here for more details - https://confluence.atlassian.com/jiraportfolioserver024/showing-portfolio-custom-fields-in-jira-software-934716200.html How to use JQL search with custom fields You can use the JQL search to find the 'parent link' and 'team' custom fields in JIRA. Go to Issues (in header) > Search for…

Hello Alex, Try in advance search - "Team" = "<team-name>"

You are doing right thing. I have done something similar at a client wherein one workflow is is supporting both dev and deployment. Once dev phase is over the issues are moved to done on the board and the "done" column of the board is mapped to "ready for deployment" workflow status and that automatically publishes the…