Matheus Fernandes Atlassian Team

Anytime. Let me know if you need any further help with this. :)

Jason, You can achieve this my creating different workflows (e.g. one for bugs and one for stories). In the Bugs Workflow you leave it as it is, and the Stories Workflow you can set properties on the steps as per this blog post in order to remove the permission to delete the issues. That is, you'd need to add a…

This is available here: https://marketplace.atlassian.com/plugins/com.atlassian.translations.jira.inproduct However, this plugin is only compatible with JIRA 6.0, so if you are using JIRA 6.0.x you won't be able to find this throught he Universal Plugin Manager. However, I've tested this a bit locally, and it worked for…

Yes, it is. You can just follow whichever upgrade method suits you better as described on: https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA Cheers, Matheus 

Hey there, You should be able to configure the detail view by accessing your Board » Configure » Issue Detail View screen. That being said, this particular field it's not possible to add as this is already present in the issue summary on the board. i.e. You have 'Issue Type', 'Priority', 'Key' and 'Summary' directly on the…

Hi Nikhil, The project leader can be changed through the Administration » Projects » Platform API » Roles (tab). You can also change the ownership of filters as per our Managing Shared Filters documentation. Cheers

Hi, Nanda. You can possibly do this using the "Behaviours" which is now bundled on the Script Runner: https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner

Hi Marco, You'll need to create a screen that will be used to display the fields in the Issue View page. If you wish, you can just copy the default screen and then remove the "Aggregate status" from the copied screen. Then, you'll need to "Associate this screen with the Issue View Issue Operation". I hope this helps!

Also, if you want to change from http://hostname:8080/jira to http://hostname:8080 or to any custom URL, you will need to change the JIRA Options in the General Configuration (Administration » General Configuration). You are prompted for the Base URL during the first step of the setup through the browser, right above the…

Dan, JIRA will show you a wizard to migrate any issues in statuses that do not exist in the new workflow, and issues in statuses that continue to exist will remain in those statuses. As for the backup, create both an XML backup and a dump just to be safe, and possibly a copy of your JIRA Home in case you need to revert the…

Hi Ivan, This happens because JIRA actually stores the username rather than the display name in a user picker custom field. See https://jira.atlassian.com/browse/JRA-31023. You can use a rest call to get the Display Name from the username: https://docs.atlassian.com/jira/REST/latest/#d2e4676. I hope this helps!

Pedro, those are in the workflow itself (there are properties for steps and transitions in the workflow) see https://confluence.atlassian.com/display/JIRA/Workflow+Properties

Actually, you should be able to edit that directly through the UI in the workflow, see confluence.atlassian.com/display/JIRA/Workflow+Properties

Hi Victor, This particular property, as well as any sd.* properties are used specifically for JIRA Service Desk in its built in workflow. Service Desk has a feature that causes issues to automatically transition from the 'Waiting for Customer' status to the 'Waiting for Support' status whenever the reporter of the issue…

See Receiving Search Results via Email

I don't think so, as JIRA does not allow you to search based on startOfDay() + Time (JIRA only allows full date formats). I believe the best you could do is setup a filter as "IssueType = "Blocker" AND Created >= -3h" and set a filter subscription for it to run at 9AM every morning. Although not as desired, this should get…

Rhonda, There's no release version defined yet - see this page, but will have the fix for GHS-6471 once it is released. Cheers

Rhonda, There's no release version defined yet - see this page, but will have the fix for GHS-6471 once it is released. Cheers

Hi Rhonda, This happens because JIRA Agile 6.4 is not yet available for standalone instances (it's not yet available on our marketplace) - the previous JIRA Agile 6.4 version that was released contained a critical bug and therefore was pulled out of the marketplace. You should be able to download it again from the UPM as…

It is possible to do this by utilizing the Script Runner add-on. You can see on this page from their docs how to do this: Fast-track transition an issue. You'd probably just need to create a custom field (e.g. checkbox field) to select if the issue should be automatically resolved or not. Cheers, Matheus

Maurycy, If you're looking for a specific type of update (if the status changed, for example) you can use the 'CHANGED' operator. You can query using: status CHANGED AFTER "2014-06-01" BEFORE "2014-07-01", for example. See https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-CHANGED I hope…

If you create a new backup from the source and try to import it again in the target instance, does the same problem occurs?

Webteam, Try using jira.permission.attachdeleteown.group using an inexistent group, or to another role. This way the reporter also won't be able to edit this. I've created a bug report as this indeed doesn't seem to be working: https://jira.atlassian.com/browse/JRA-38878 Let me known if this helps.

That is probably because of the required user mentioned on the screenshot you attached :)

Hi, Hool. This is a limitation of JIRA, and a suggestion to improve this is being tracked on: * https://jira.atlassian.com/browse/JRA-28748 The project import should work nonetheless even though those fields won't be imported. As for workarounds, from what I saw they all rely on some development. Still, you should be able…

More precisely, this function of the Script Runner plugin: Rename a User ID On the User Interface, you'll have an option to Rename and user and to Merge two different users into one.

Hi, Aleksey, May I know if can see the following on the JIRA logs: Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled. I believe this may be related to the CompilerThreads using so much CPU. This behavior is fully explained on this blog post: We don’t have any statistics as to the…

Hi Ronson, The answer would be "Yes" - this folder contains JIRA Automatic backups, JIRA backups (you created) and Support Zip files so they can be deleted. That being said, rather than deleting them, I'd advise you to at least move a couple of those to a safe place as they, well, have your backups. Cheers, Matheus

Depending on what change you are trying to make and the version of JIRA you are using, you can simply create a draft of that workflow, and then publish the draft. See https://confluence.atlassian.com/display/JIRA060/Configuring+Workflow#ConfiguringWorkflow-Editingaworkflow

Just keep in mind the restrictions when editing a active workflow: Please note that the following limitations apply when editing an active workflow (i.e. a draft workflow): * It is not possible to edit the workflow name (only the description) if a workflow is active. * Workflow steps cannot be deleted. * A step's…