Daniel Ebers Expert

Hi @Gavin Klose looks I am quite late to the party - but agreeing to all what Dirk said I just wanted to post a popular bookmark, the video library. Here you can find tons of videos - that, although not helping for the current case, could be of support for later actions in configuring Jira. * Check out the Community video…

Hi @Brendan Gray adding to the great advise of BB8 - please keep in mind that the "Free" plan (which you seem to be using according to Community tags) does not allow anonymous access. In case it is a hard requirement you would need up upgrade to a paid plan. Regards, Daniel

Hi @Hieu Nguyen from your last question I hope to understand it right - you will per default see all sprints but you can select a specific one from dropdown (in your case 1-3). When viewing all sprints, they are not separated - in order to get this a sprint must be selected (one of the currently three displayed in the…

Hi @Jayde Wofford using Teamlead calendar in the past I am not sure if the JQL queries work on non-jira events like you said. However, I can confirm their helpdesk is great - so in case you won't receive an answer here the following days please consider raising a support request with Teamlead. Regards, Daniel

Hi @Michelle + @Ekaterina Kobernyk + @James Yoon just wondering if there is some commonality in the browsers you use? For example - Chrome, Firefox, but on which version? The reason of the question is just the idea if a recent upgrade (most of them present nowadays updates link 'we have a new version for you restart and…

Hi @Sébastien PATTE according to the documentation and previous knowledge the appropriate location to change the port is the file "server.xml". Have you had a look into this one? If useful here is the appropriate documentation for changing the port: * Changing Jira application TCP ports…

Hi @Asher Francis when you say "permission helper" looks good I am wondering if the Reporter is on edit "Edit Screen" for the project in question? Could you please kindly check? Regards, Daniel

Hi @Eric Keating is is a team-managed project or a company-managed project (the project will tell when you open it and for example looking on the issue navigator, on the bottom left). I remember a report here in Community that with team-managed projects the "People" field is not working for this very type of gadget.…

Hi @Hoc it is a different naming. You will find timelines in Jira Work Management projects - but the "basic roadmap" in Jira Software projects. You can learn more about it here: https://www.atlassian.com/software/jira/features/roadmaps Please note that there is also a product called "Advanced Roadmaps" which is available…

Hi @Carissa Massongill just in case you have not seen the specific part in documentation for "Reporter" I wanted to add that there is some speciality: To have the reporter field default to the currently logged in user, the user must be logged in and must not have the Modify Reporter permission. So I think you could leave…

Hi @Jean Bien-Aime this sounds like a bit of a catch-22 situation. As for your ask - yes you could raise a support request with Atlassian, however only site administrators can do it and it looks the accounts you have still have no permissions to manage users (and no permission to access to support requests). In the first…

Hi @Nedviga in case your URL looks like xxx.atlassian.net you can be sure it is a Cloud instance - server ones look rather like this: jira.example.com What you are looking for is probably possible but not easy by any means. Assuming your users have properties set (as Jira needs to know who the deputy is) - probably this is…

Hi @Todd Holman in the following query there might be missing a thing because I fully believe Ismael when he says it is not possible out of the box - but anyways, currently not seeing _what_ could be missing as in a test instance it seemed to bring up the correct results ... so you could at least give the following a try…

I would assume so - the green slider is, from what I know, the right 'switch' to determine the behaviour. Feel free to observe if the behaviour is now how you expect it to be for your setup. In case there is still something open kindly report back here, Community members are always here to help :)

Interesting, so probably the SourceTreeSetup-1.10.15.4.exe was an old(er) version or a different product - it just does not want to fit into the 3.x.x version scheme. Good to hear the situation now looks better! Well done!

Hi @Magdalena Zhisheva putting them into "Browse Users and Groups" is a perfect first step. There should not be missing much. Can they tag absolutely nobody or only some people? The only thing that I could imagine being still missing then is that the people that should be tagged/mentioned are not able to see the issue -…

Configuration for the "Request by email" Request Type can be tricky as Jira must be able to read subject = Summary and Mailbody = Description - making more fields hidden/required can lead to non-parseable mails. What is the current status with your configuration when you say it does not work? Can you open a request of type…

Thanks for clarification. I can see Earl answered with a great and detailed follow-up which is meanwhile an accepted answer - just in case somebody else is looking for the same and reading here. Regards, Daniel

Assuming 7.13 is referring to your Jira version it is too old - in cloud it would be also available (just adding this as you are touching cloud in the last sentence). Regards, Daniel

Hi @Jodie Sleeman it is available when you choose "Edit issue fields" as an action and there expand the "More options" dropdown. In "Additional fields" you need to clear the example values and then insert the code Ravi suggested. You can see above how it should look like. Regards, Daniel

Hi @Josef Sigl you are correct with your observation and there is no option to bring back the old "view". There are some Apps from Marketplace which promise to display the roles in the old fashion but I haven't had a look into them. There is a Suggestion to bring back the old view - from my very personal opinion this is…

Hi @Jean-Christophe Rase adding to what Nic said we found documentation fot the API of UPM (which manages the Apps in the background) here: https://ecosystem.atlassian.net/wiki/spaces/UPM/pages/6094960/UPM+REST+API Probably this helps to get a first insight in the Apps installed on your server in a programmatical way.…

Hi @Muhammad Umar assuming Rob summarized the situation in total completely already - there should be an option to do so by querying for the sprint using JQL like Sprint = "My Sprint 1", then locating the relevant issues and set the Fix Version/s / Affects versions per bulk edit. Just to prevent misunderstandings ...…

Hi @Richard Way presumable this Suggestion describes what you are observing: * Parent Link field shouldn't allow users to select closed issues https://jira.atlassian.com/browse/JPOSERVER-2346 Seeing this Suggestion aims towards Advanced Roadmaps on server it could make sense to either comment the Suggestion over there or…

Completed :)

Hi @Julie Bashara the screenshot seems not coming through - so just a question: is it the "Invite users" dialog you are referring to? Source: https://support.atlassian.com/user-management/docs/invite-a-user/ Other than that I am familiar with the switch ("green slider/switch") on this page which says if an user should get…

Hi @Lars Blaschka as Trudy suggests an App will be of great help - the core question might be: do you already have Apps enrolled in your instance that are capable of supporting the use case? Coming across a similar request in the past Script Runner (there: Scripted Field) could be of help, the user implemented it as…

Hi @Gopal Kasat adding to what Nic says for the filesystem permissions of the file (foremost probably the one in the error message, /var/atlassian/application-data/jira/plugins/.osgi-plugins/felix/felix-cache) please consider checking the system's overall health if the permission check should not turn out any obvious…

Hi @David Jung not sure if I am getting the full use case right. Assume you are the vendor of a product but you have a cooperation with a different company - this is what I understand so far at least. They will need to open requests in your company's Jira Service Management but should not see requests from, let's say other…

Hi @Thomas a test on a demo instance showed that in that case users (those of Organization 'c') get the same permissions and possibilities like the user that raised the request initially. In order to share with an Organization it seems to be required to add the Organization to a JSM project. Also all users are part of the…