Tomáš Vrabec_mlkuef Rising Star

Founded! Atlassian solved this within this issue https://jira.atlassian.com/browse/JSDSERVER-6402stuck for few hours with them too. Just upgrade the JSD.

Hi, Atlassian solved this within this issue https://jira.atlassian.com/browse/JSDSERVER-6402 stuck for few hours with them too. Just upgrade the JSD.

Guys did you figure it out? Got very the same issue. User A is able to hit transitions. User B which is very the same customer cannot do that. Users are identical in point of config view, working with the same ticket. 

Tip for everyone in here: Just install free add-on Relative time converter from @MoroSystems Support Link: https://marketplace.atlassian.com/search?query=relative+time+converter

Hello Kubilay, Can you please provide step by step procedure of both the alternatives? We are going through with the same problem ever since migrated to new instance. Or maybe - how about to post it publicly? ;-) 

Yesterday was too late! Finally I will get much more easier job with debuging corporates exceptions with IE11. Thanks guys for that move!

@Nic Brough -Adaptavist- thanks for that even in 2019 Not sure if its funny or sad, but if you run issue.getStatus().getStatusCategory().getName() over an issue which is in Status which is "Done" Status Category you will get a string "Complete" ¯\_(ツ)_/¯ Thanks man!

Hi. Don't want to offend you, but Its 2019. My most up to date CV is from 2011. If there would be potential for remote freelancer with traveling, check my profile at https://www.linkedin.com/in/tvrabec/ Cheers, Tom

Guys this is know "feature". Please do votes and comment at https://jira.atlassian.com/browse/JSDSERVER-3855 I cannot imagine that those stupid features even exist ...

My two hobbies on four pictures :-) Guess that no description is necessary :-) 

@JiraJared solved with slightly modified code import com.atlassian.jira.component.ComponentAccessor // Get the current user def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() // Get the Requestor field def requestor = getFieldById("customfield_10301") if (requestor.formValue == "") {…

They can do change on the create. The point behind this is to not disturb user by filling this, if they are requesting on their own behalf, but give them option to change that, if they are requesting on behalf of someone else. Will try this one, not skilled with this level of scripting at all.

The reason is bug in Jira https://jira.atlassian.com/browse/JRASERVER-35622

Whoohoo. Catch me if you can! https://www.linkedin.com/in/tvrabec/

Hi Lara, yup, we thought about that as well, but as you got thru consequences there is more pain then benefits :-( 

Hi Lara, yep, we are now considering two main options, as upgrading to 10k license tier is not in the budget. 1) customer listener in script runner 2) custom notification scheme in JETI Just curious, that JSD never counted with an option to be internal service desk where agent are also customers.

Hi. Will take it in points. 1) we are working on project called “IDEA Portal” where everyone in company can submit an idea and everyone have to be able to see others ideas. Agents then can promote ideas to tasks. Agents can submit ideas as well. 2) we removed original notifications with customs, thats not a problem.…

Hi, how about a simple workaround? 1) Remove priority from edit screen at all. 2) Create independent self-transition called "Change priority" 3) Make a condition for this transition only for particular roles. 4) Include Priority for the transition screen.

Can confirm Scotts thoughts, from the principle of showing list of boards there is no known way how to that. As far as I know.

Thanks, had a very same issue! 

Nope. You did something, which is again agile rules. After sprint is started, you should never touch the scope OR if there is some blocker you have to solve, you have to put it in running sprint BUT you have to REMOVE same amount of scope you added. So the answer is No and its expected behavior.

Well there is one option I like the most. 1) Create self-transition (from and to same status). 2) Add post function create subtask & requested automation or screens to be filled. 3) If your automation plugin request transition subtask to same status as parent. (Workflow had to support this). BTW: I always I always used to…

Nic mentioned almost everything, from my expirience I do recommand using JIRA based Roles (instead of Groups) in combination with Persimssion Schemes. This worked best way in all my projects / clients.