Tuncay Senturk _Snapbytes_ Community Champion

Also, you can raise a support ticket here to get vendor support.

Hello Derrick, First, you can use Issue Navigator to filter those issues project in (PROJ1, PROJ2) and resolution is EMPTY This filter returns all unresolved tickets for both Proj1 and Proj2. You can add as many columns as you want to issue navigator, get excel export as well. Also, you can save this filter and use it in…

That's a tough issue, but you can have a look at Jira Performance Tests here. It automatically provisions a Jira instance in AWS infrastructure and does performance tests. I hope that helps

Hello Hugh, You can't change the name of the Summary field unless you use scripting. You can use Script Runner Plugin (Behaviors) and type some script to change it. And, you can't remove the Summary field. Best

Hello Rachel, Without a plugin, there is no field level security in Jira. However, you can think of a workaround with workflow permissions. You can add "Self reflecting transitions" with a permission to admins only. Self reflecting transitions are the transitions in which origin and target statuses are same. For instance…

Hello Damien, After adding new SLAs, you should generate SLA data for already existing issues. Please go to TTS menu > Generate SLA data page, write JQL for those issues and proceed. If you still have problems please raise a ticket here and our team will respond ASAP. Regards Tuncay

Hello Josh, Yes, there is a way to do that. * Go to the Advanced search view and search for issues to move * Select the options button (3 dots in top-right corner) > Bulk Change... * Select the issues you'd like to perform the bulk operation on, and select Next. * Select Move Issues, and select Next. More details here

Also you can use free Easy Integrations app's post function. Here you can see a brief documentation on how to do that.

You can add a post function calling a REST service to raise ticket in your other Jira instance. You can use free Easy Integrations app to do that. You can write groovy script to filter which issues would call the REST API. However, it is best to have both in single instance, this way both SD and SW issues will have a link…

You should add some js code that you used in your plugin. Devil is in details.

Hi Joseph, AFAIK, you can not just update issue type. You should move issue to change issue type, because changing issuetype changes the fields, workflows, screens, ... If you want to change issuetype you can use REST API so that you can change multiple fields at a time.

Glad to hear that it worked

Hello Eric, Although it is really hard to understand your question, the JQL is valid. is NOT EMPTY means that there is an indexed value for the field. So it is not null, but can be blank string if indexed so. 

Currently, JSD does not support complex customfields. It does not render either the vm file or the js codes. It wraps your whole implementation. Anyway, there are low level tricks to handle this but I think it is wise to wait for Atlassian solution for this.

Hello, In Java, default number conversion is int, so if you do not cast any of the variable to double you will loose the floating part. Use Double.parseDouble for each or for at leas one. That should make the trick. Or cast : a + b + c / (double) d where a,b,c, and d are your Integer.parseInt statements. Tuncay

Hello, You need to add a condition into your web-item in atlassian=plugin.xml <web-item .. <condition class="com.mypackage.MyCondition" /> </web-item> Here is the snippet of the condition class public class MyCondition extends AbstractWebCondition { @Override public boolean shouldDisplay(ApplicationUser user, JiraHelper…

Hello, AFAIK you can't do that in Jira out of the box. If you have Script runner plugin, you can use below JQL issueFunction in epicsOf("PROJECT = HakunaMatata AND issuetype in (Story) and Status in (Open)")

Hi Andreas, fieldLayoutItem was defined in your code. And you're right about the latter one, it has three args. Assuming you have the issue, the final code should be like this: import com.atlassian.jira.issue.fields.NavigableField import com.atlassian.jira.component.ComponentAccessor; import…

I'm not sure but please try below code. I did not test it, just give it a try It may give a clue import com.atlassian.jira.issue.fields.NavigableField Field field = fieldManager.getField("description") NavigableField navigableField = (NavigableField)field return navigableField.getColumnViewHtml(fieldLayoutItem)

Hello, The more details you give to clarify, the more answers you get from the community. AFAIU, you need to calculate the number of days between the date which issue was resolved and the date in 'due date' field. Jira does not give you this out-of-the-box. But, you can display due date, and resolution date in issue…

Hello Mark, There may be a bug related with custom field context. Could you please raise a support ticket here? Thanks

Is X dead? Is X dying? where X is the name of really useful framework/methodology (after a while).

Hello Melissa, Try using "assignee WAS" as below assignee was User2

Hello Sam, Out of he box solution: you can create a user custom field, and fill that field in the transition post function in which the issue is resolved. Alternatively, you can use a plugin like Enhancer Plugin where Resolution User is bundled.

Glad to hear that. btw, could you please accept the answer so that other users would see it without diving into comments.

Yes, I tried leaving the field empty as in the screenshot and it cleared the field.

Hello @Sridhar Gandla Bulk update selecting (enable the checkbox near) "Due Date" option, with EMPTY field should clear the field.

You can find all documentation here. Just click on cog icon next to SLA definition and select "Pause SLA" You can find sample screenshots for pausing SLA in SLA definition page.

Hello Prasad, It is possible with Time to SLA plugin. Also it can be doable by Enhancer Plugin but Time to SLA plugin has much more features (here is the comparison for two apps) You can define SLA by priority or even by JQL with both plugins.

Hello Jackie, There is no such bundled feature. There are two solutions: * Open date is the created field. Create a date field which will hold the In progress date. And set the current time via post function. Then you can export issues in issue navigator including created and In Progress Date * You can use Enhancer…