Tarun Sapra Community Champion

Currently, it's not support to change the size of the card. You can vote here - https://jira.atlassian.com/browse/JSWSERVER-5200 

Hello Nikola, Your question is not concise enough. Epic workflows is a combination of tooling and processes. Epic generally have a different workflow then story. Epics are assigned to POs and they move the Epics based on the progress of stories by the various development teams. An epic can have easily upto 20 stories. You…

Default values of system field (like description) isn't yet supported (out of box) -https://jira.atlassian.com/browse/JRASERVER-4812 But your requirement can easily be implemented by Behaviour plugin (part of script runner add-on) Documentation here…

Hello Lisa, Since customer is the reporter, thus you can create the chart from the JQL and use an pie-chart which will give you the information whcih you want.

You can make the field optional from the field configuration screen. You can select values from the team field if you have added teams in the porfolio. If there are no teams in porfolio then you won't be able to add new teams from JIRA User interface. You have to add the teams from within portfolio.

Please see here on what is possible and what is not with the "team" field in jira https://jira.atlassian.com/browse/JPOSERVER-1847 Full docs here - https://confluence.atlassian.com/jiraportfoliocloud/showing-portfolio-custom-fields-in-jira-software-856708725.html 

You can remove the field from the create issue screen. Currently it seems the field is added on the screen thus it's showing up but as no values assigned to portoflio plan's team field thus it's empty.

Can you make sure that "Application links" between JIRA and confluence cloud is still up. https://confluence.atlassian.com/adminjiracloud/using-applinks-to-link-to-other-applications-779295829.html If it's down that could be the reason why you can't see "create jira issue" option. Then you need to raise a ticket for the…

Paste your complete query. What's the current JQL which you are using? In the current JQL you would need to append "type != test"

If the issues aren't in backlog then they won't appear in the active sprints anyway. "Test" type comes from Zephyr plugin. And lot of times, POs don't want them on the board (backlog) as they create noise.

Strange, try this - https://confluence.atlassian.com/jirasoftwareserver074/configuring-filters-889531269.html 

https://confluence.atlassian.com/agile/jira-agile-user-s-guide/configuring-a-board/configuring-filters 

Backlog shows issues which match the issue filter. JIRA boards show issues being fetch from the underlying JQL. Thus, you need to update your Board filter and add "type != test" in the filter in order to remove test type from the board. See here on how to configure the board filter…

 Atlassian switched to atlssian id for users which are using the cloud solutions. To update emails go to - https://id.atlassian.com , this shouldn't change your JIRA history and new emails should go to the new email account .

then you can export it as CSV

Add the "resolved" colum in the issue search's issue navigator. The "resolved" column of the issue search carries the information when the issue was closed.

Some more sameple - https://stackoverflow.com/questions/39483956/update-custom-field-value-using-a-scriptrunner-for-jira-custom-listener Another detailed sample - https://community.atlassian.com/t5/JIRA-questions/script-field-update-when-issue-is-created-based-on-custom-field/qaq-p/458587

This has been discussed many times on this forum. You first need to fetch the values of user pircker field and then update the drop-down field's value. Here's an sample - https://community.atlassian.com/t5/JIRA-questions/Updating-a-custom-field-using-groovy-script-runner/qaq-p/256708

Hello Maggie, Post-functions are always executed at the end of the transition phase, thus even if you assign the issue to "User1", still it will be always assigned to "A" becuase in your post-function you have configured it that way. Because the post-function is excuted after transition screen thus "A" overrides values of…

Yes, full restore you can do but not project restore between different versions of JIRA.

Yes, you can directly import XML backup of 7.0.10 to JIRA 7.3.6 . https://confluence.atlassian.com/adminjiraserver071/restoring-data-from-an-xml-backup-802592998.html#Restoringdatafromanxmlbackup-restorexmldata Please keep in mind you need to have same custom fields configured and plugins installed. otherwise you would run…

Hi Vivek, But isn't the default public mvn repository automatically looked-up. Generally the need to additional repos is for jars whose version aren't available on public mvn repos.

Please see this - https://mvnrepository.com/artifact/com.atlassian.jira/jira-rest-java-client-parent/4.0.0 <!-- https://mvnrepository.com/artifact/com.atlassian.jira/jira-rest-java-client-parent --> <dependency> <groupId>com.atlassian.jira</groupId> <artifactId>jira-rest-java-client-parent</artifactId>…

The reason all "in progress , schduled issues are gone" because in your filter you have added the criteria "AND resolved >= -10d " This basically means, issues which have been resolved in last 10 days. Thus, you are fetching only resolved issues. Hence other issues have dissapeared. 

Then checklist plugin would be suited for the task. As you can add various tasks on the story and they have to be checked before the story is actually closed.

Hello Krithica, What you ask for a common scenario. Sadly, as of now there is no way to do it out of the box in JIRA. An answer here explains to use custom javascript for implementing this - https://community.atlassian.com/t5/JIRA-questions/Hide-select-lists-of-Project-and-Issue-Type-from-the-Create/qaq-p/241794 There…

Hi Ahmed, I understand the issue which you are facing. I have implemented a solution to a similar problem at a client. First, write down all the tasks that are common for most of the Epic/Stories which the team is working upon. It can be taking approvals from build team, release team, Finance team etc. basically all the…

Backlog is now available on JIRA software server 7.4 Release notes here - https://confluence.atlassian.com/jirasoftware/jira-software-7-4-x-release-notes-902079634.html 

See the code here, try from here https://community.atlassian.com/t5/JIRA-Core-questions/Script-Runner-Transition-parent-issue-based-on-subtask-status/qaq-p/63722

The Scrum board doesn't support initiative/theme . There is a dedicated Epic panel but not for types above the Epic level i.e. in your boards you will get story and initiative at the same level if you use the simple filter (project = X) thus you need to use a filter which ignore initiatives in scrum boards. As they are…