Tarun Sapra Community Champion

Generally, validator/condition are associated with issue workflows. But in your case you want validation based on already existing issues i.e. you don't want the issue to be created if an issue with a similar summary already existing. Thus, in the validation section of the issue. You will need to write a validator which…

Have you tried using JIRA portfolio? https://confluence.atlassian.com/jiraportfolioserver/managing-portfolio-dependencies-802170496.html

For multiple sprints you can use "Sprint in ( )"

You can use JQL to fetch issues and then download the report in CSV format. Basically, you can JQL like - status changed from closed to open and Sprint = "<sprint name>" and type = Bug

Using script runner plugin it's pretty straightforward. issueFunction in parentsOf("assignee = currentUser()") 

I don't understand the language in the screenshot but it seems it says "Description is mandatory" so in the field configuration scheme of the issue you have the description as mandatory but the description field is missing from the screen scheme. Thus, this error. Basically you are making a field mandatory but not adding…

Hello, What's the exact issue can you please provide more details? As from the screenshot it seems fine. In JIRA you can create 3 types of projects - Business, Software and Service desk(is the SD application is enabled)

Tempo Timesheets plugin(paid) is a good way to do it.

H/W (assets) management in JIRA can be done using "Insight" plugin in JIRA. https://marketplace.atlassian.com/plugins/com.riadalabs.jira.plugins.insight/server/overview

Try adding the binding jar file <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-jdk14</artifactId> <version>1.7.25</version></dependency>

Status is changed via workflow in JIRA and editing the screen. Thus, if you wish to change the status then you have to click on the workflow button.

Please contact atlassian support for this purpose or post the exact error which you are facing. As this forum is mainly for QnA and knowledge sharing among community.

Hello Sven, This isn't possible in JIRA out of the box. As permissions are based around issue operations(create, edit , updated etc) instead of specific issueTypes. https://jira.atlassian.com/browse/JRASERVER-5865 Still, with the use of plugins this can be achieved. Using client side JS this can be done with Behaviour…

Using event.getUser() you can get the author of the event and then populate the custom field with that value https://developer.atlassian.com/static/javadoc/jira/latest/reference/com/atlassian/jira/event/issue/IssueEvent.html#getUser()

https://scriptrunner.adaptavist.com/4.3.5/jira/listeners.html#_custom_listeners https://developer.atlassian.com/jiradev/jira-platform/guides/other/tutorial-writing-jira-event-listeners-with-the-atlassian-event-library

You need a custom listener or if you have script runner plugin installed then you need to implement an listener, which listens for issue update events and updates the custom field with the name of the event author.

The presence/absence of fields on the create screen depends on "Screen scheme" , thus please check your screen scheme for the issueType. Field configuration scheme is primarily meant for making fields required/optional/hidden.

Also, make sure all the values are mapped to the right project context. As in custom field you can have different set of values for different projects based on the context configuration.

It could be an indexing issue, if you reindex jira and then check again.

https://community.atlassian.com/t5/JIRA-questions/Behaviour-plugin-doesn-t-pickup-the-time-value-while-fetching/qaq-p/300034

Possible duplicate 

In the "user directory" section of JIRA and Confluence disable the option of "JIRA internal directory" and for confluence "confluence internal directotry" Register the AD in crowd and do group management in crowd. i.e. Authorization via crowd and let crowd delegate authentication to AD and crowd also pulls users from AD.…

Possible duplicate - https://community.atlassian.com/t5/JIRA-questions/Can-we-add-extra-button-to-the-default-screen-Create-Issue/qaq-p/205023 

To implement this functionality you would need to do some coding and write your own plugin. An alternate is to create a loop-back transition called "create sub-task" which return the user to the same status and when a user clicks on the transition button then in the workflow post-function a sub-task is created.

As of now, JIRA by default doesn't support it. But if you have script runner plugin installed then you can do it via the following JQL project = X and issueFunction not in hasLinks()

If by *linked issue* you mean no related Epic then you can use the JQL project = X and "Epic Link" is empty Here project X can be your project having ideas

Sure welcome! Just in case if you want to fetch issues which have partially resolved linked issues i.e. if 2 out of 4 linked issues are resolved then you can drop of the second part of the query and use only issueFunction in linkedIssuesOf("resolution is not empty")

This works fine, for fetching issues which have *all* the linked issues as resolved. issueFunction in linkedIssuesOf("resolution is not empty") and !(issueFunction in linkedIssuesOf("resolution is empty"))

It could be a bug that comes up occasionaly, please raise a ticket in support.atlassian.com if you see the bug again.

Well, this looks like Javascript bug, raise a ticket in the support portal. https://support.atlassian.com/