Tomáš Vrabec_mlkuef Rising Star

Hello @Moin unfortunately this is not possible, since the suggestion were reconsidered as security bug. You can still raise a new ticket within Atlassian support a put there a link for CONFSERVER-59730 and / or this article :-) Hope this helps. If I will receive any further informations about this issue, I will update this…

Good news everyone! Suggestion was reconsidered as security bug! Hopefully this will be fixed in near future!

Script runner "Copy Project" will copy also the Custom Field Context. 

Ahoj @Martin Bayer _MoroSystems_ s_r_o__ My final version looks like this: if (members != null) { def userInsightField = customFieldManager.getCustomFieldObject("customfield_11525") // TSO members (Insight) for(item in members) { def member = iqlFacade.findObjectsByIQLAndSchema(3,"\"User Jira Key\" = " + item.key)…

As I am reading all of your concerns and comments, I cannot help myself. I am a freelancing Atlassian Architect / Consultant. This year I migrated 3 companies from Cloud to Server. If you are interested to do that as well, do not hesitate to reach me :-) https://tvrabec.atlassian.net/l/c/k7xksiHr

This is such a fail. I do have few customers who stayed on Cloud only because of old view. For example, typical deal-breaker is the fact, that sub-task are not counted into parent. JRACLOUD-70150 this is not the best step guys ;-) This year, I migrated 4 companies from Cloud to Server. You are going in wrong direction. 

Hi. You are looking for permission scheme settings. if I understand it correctly, only reporter can close issues. Not even assignees. This could be achieved by assigned permission "Resolve Issue" to "Reporter" only. Regarding transition specific to assignee, look for the permission "Transition issue" and put there…

Do a copy of a workflow, in this copy, create new transition, then assign the copy of original workflow to workflow scheme instead of the current one. Example Workflow_scheme_project ---- Workflow_without_reopen Create Copy_of_Workflow_without_reopen edit Copy_of_Workflow_without_reopen and add transition do mapping of…

Note to future myself: It is better and easier to iterate in this way: def sb_url = [] String query_sb = 'JQL' // edit this query to suit def query_sb_parsed = jqlQueryParser.parseQuery(query_sb) def search_sb = searchService.search(user, query_sb_parsed, PagerFilter.getUnlimitedFilter()) def search_sb_total = ("total:…

you have to go to your site configuration - issues - workflows - edit this workflow - create a transition from Done to Open ... I am not able to help you with Jira in your language, sorry :-( 

Yes, we can understand. No need to use capslock. We would like to help you, but you need to change the configuration of your workflow.

Perfect, so thats mean, thats it is build in the wrong way. Post here the screenshot of workflow configuration ;-) 

Yes, this is true. Component is an object with properties. One of those properties is also "Name" and "ID" as the Name could be the same across the Jira, the ID will also be unique. So each and every component is different object. It is possible to resolve this via custom script on the server, but unfortunately I am not…

You need to go to configuration for this particular issue type / workflow a find configuration over there. It is possible, that there is no transition back at all. Can anyone else do this transition, or noone? Who made the workflow? Is it custom or built in?

It really depends on setting of that transition. Could you provide a copy / paste or / and screenshot of that transition validator / post functions list? 

There is an active feature request for this. See https://jira.atlassian.com/browse/JRASERVER-59132 Or https://jira.atlassian.com/browse/JRACLOUD-59132 Looks like no workaround exist at the time. 

What is your mail server structure look like? Is it IMAP? spaces wont work. Try to create new folder called just the Folder and go with INBOX/folder (case sensitive)

Its a long time sice I moved from Scrum Master role, but I would suggest you to run a test project in Jira and try to "emulate" a common 1 or 2 or 3 sprints. With everything. Grooming, Planning, Estimation, Retrospective, Documentation, Statistics, predictions, reports ... just it at max, it would be enough ;-) 

Well I did not prepare at all. Worked as scrum master with Jira for 2+ years and learned everything needed. Generally I can suggest to go thru most of the business usecases from the point of poweruser view. 

Sad decision. IE11 is deprecated even from their authors - Microsoft. You should definitely ban this browser. Because of security, compatibility and mainly because of developers and admin, who has to debug and workaround stuff, which is working in every other 21 century browsers. 

UPDATE: With support we found out the the issue is caused most probably by documented bug at https://productsupport.adaptavist.com/browse/SRJIRA-3918

With support we found out the the issue is caused most probably by documented bug at https://productsupport.adaptavist.com/browse/SRJIRA-3918

Funny. Another customer need this, so I google for solution and founded my unanswered question from year ago. Great. 

I am already on my way. Paid hotel and flights from my own pocket, will not receive any money back, everything prepaid. So I will finish my trip and stay in Vegas for those 5 days .. 

Maintenance extension is not a way at all, it would cost much more then brand new licenses after 2+ years :-( 

To change Project Category, you have to be a member of a group, which do have Permission of Jira Administrator or Jira System Administrator. 

There are few limitations within Adaptavist Behaviours and I think that you are trying to achieve one of them. Screens Behaviours function on the Create Issue, Update/Edit Issue, Assign Issue, and Workflow Transition screens. On the View Issue screen, trying to edit a field with a behaviour will launch the edit issue…

Hi @Damien I am not anymore involved within this solution partner, but still do have a lot friends over there. Lets try to tag them, and hopefully someone will take care about your suggestion :-) Hello @MoroSystems Support could you take a look this suggestion? Relative Time converter should be maintained as its very…

Hi, please check you JSD version, if its lower then 4.4.0 then upgrade it. There is a known bug with unwanted behavior in case you revoke Modify Reporter permission for customer portal in older JSD. See https://jira.atlassian.com/browse/JSDSERVER-6402 this is only one of many usecases affected by the bug.

I am in, got client with 10k user tier on server planning to migrate to cloud ... well, they already started with PoC. And its not the only one who is considering this :-)