Tarun Sapra Community Champion

Hi @Jobin Kuruvilla Quick question, The connectAll adapter will be required to be bought for both HPQC and JIRA in case of their integration? or Do we need only HPQC adapter and that will use JIRA REST API to create the issues in JIRA i.e. no adapter at JIRA side required? I am trying to understand the installation of…

thanks! , can you please furnish more details!

works, thanks!

Hi bvce, The only Major problem you can face is regarding the plugin compatibility as since JIRA 5.x onwards the default plugin system is type 2 and loads of changes have been made in the plugin APIs. Thus if you have lot of plugins just do lot of testing before actually migrating the production system. I migrated a huge…

Hi Matthias, You already have the right filters - one of the issues i feel can be with the filer - Time that tickets spent in various stages of the workflow per project As developers don't "click" on start progress once they actually start progress and loads of times they do open-> closed thus this kind of behaviour can…

Hi Fahad, Create a JIRA email handler see here - https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email Make sure your emails for a certain project are being sent from the project email which is same as the one configured for the handlerr. You can set project email from the project admin page.

Status based permissions don't exist in jira out of the box. You need to provide read permissions as they are validated first and then workflow conditions come into play.

I am planning to write a python script, wherein the newly imported issues carry their original issueKey in an custom field and the script would copy the attachment based on the original issues key from the source instance and attach the attachment file to the new issue in the target instance.

I am facing a similar situation, Did you manage to find a way out of it?

I actually was avoiding using any plugin for the same, as this plugin is the first to comeup on the market place when we search "bar charts"

You can use "Cross project Releases" feature from the Portfolio - https://confluence.atlassian.com/jiraportfoliocloud/creating-and-configuring-cross-project-releases-828785313.html As now you can create one release across all the projects using portfolio.

Your question is pretty broad. My suggestion to you will be to create a plan and set it's source as the scum/kanban boards. Once you have all the presently active issues in the Portfolio, you can explore other complex features like Capacity planning, Release planning, skills/teams management. etc But first choose the right…

ok i got confused by the KB aritle which states about putting the post-function update at the beginning - https://confluence.atlassian.com/display/JIRAKB/The+'Update+Issue+Field'+Post-Function+Doesn't+work+when+Creating+Issues+after+Upgrading+to+JIRA+6 thanks!

My advice - always refer cutom fields by IDs and this worked for me in one of my scripts - customFieldManager.getCustomFieldObject("customfield_11550"); So if you go to the link you have shared you can use the ID of custom field and you can know the ID of any custom field by going to it's edit screen and the ID wouuld be…

Since it's a cloud instance thus your best bet is to contact Cloud Support team from Atlassian, but from the error it seems that "Raised during" is a mandatory field in field configuration but missing from the Screen definition thus you are not able to create any issue as it's mandatory but not visible on creation screen…

Here's a usecase - https://answers.atlassian.com/questions/256156/transition-a-ticket-between-workflows-support-workflow-to-development-workflow

And here's a code sample as well for your usecase - https://answers.atlassian.com/questions/250963 

There is an open improvement as well for your request - https://jira.atlassian.com/browse/JRA-29839 

Hello Marty, JQL is meant for searching across issues based on criteria which is simply value of issue fields like project, type, resolution etc So what you want isn't possible as the transition date is part of the history of the issue which isn't displayed on issue fields on the view issue scree, The easy way to actually…

Hi All, We are also facing this issue wherein users are automatically added to crowd, we are using Crowd 2.4, though they never count towards license as you need to be part group for that but still importing such a large list of users by crowd from ldap just doesn't make sense.

Hi All, We are also facing this issue wherein users are automatically added to crowd, we are using Crowd 2.4, though they never count towards license as you need to be part group for that but still importing such a large list of users by crowd from ldap just doesn't make sense.

Just to add to Ricardo, has a new field by the name of "Story points" also appeared, as sprint and story points are custom fields part of JIRA Agile (formerly greenhopper)

it was network issue, it's fixed now.

https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/server/overview

It's achievable using Script Runner plugin linkedIssuesOf function https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html JIRA Agile users can query on epic links, eg find all Epics that have unresolved stories: issueFunction in linkedIssuesOf("resolution = unresolved", "has Epic")

Yes, it's Issue assigned event as well as Issue Updated when issue is reassigned- https://jira.atlassian.com/browse/JRA-29328 As per Atlassian it's two events, Issue Assigned as well Issue Updated " Both events are now sent such that people notified of all issue updates will continue to receive them and people only…

Hi Boris, Yes, I knew about the AUI, but my only doubt was whether there is some trick to sneak in and <b></b> or something for the text. Yes, I agree with you about staying away for custom JS for JIRA. Thanks.

What's your question? If you want to customize workflow you just need admin rights and basic knowledge of workflow https://confluence.atlassian.com/jira064/configuring-workflow-720412524.html

The script runner plugin has a built-in script for "Copy Project" that can be used for creating projects from a project template. That's what I use.

Hi Mukul, You are trying to to use Epic LInk field which is a field on the story issue type and not the epic. If you have script runner then you can easily use story key to find connected epic using issueFunction in linkedIssuesOf("key=PG-02", "has Epic")