Bastian Stehmann Community Champion

Nic is right, they can change it. But if you fear, that your Admins will change the scheme to get access, get that secret data and then change it back so that it is not obvious that they did, you should maybe think of the kind of people that are administering your system. 

Hi @Fabian, welcome to this community. It is right, that a admin always can access all projects (he will have to to do his work). But you can use issue security to set security levels on that issues. If you do not add the Admins to the security levels, they won't be able to see the issues, although they can access the…

Hi @Ciampa, what do you mean that you have created a structure?

Hi @Lakshmi Narasimhan, welcome to this community. In very short you can add that as description to the project. If you want to describe it more detailed, I would suggest to describe it somewhere else (for example confluence). There you can also add links to stories. You can add the link to the confluence space/page as…

Hi @Akshay Laykar, I am sorry but I don't know any way to do this without addons.

Hi @Swarnima Srivastava, and welcome to our community. Do you want to try Jira? Then you can sign up here for evaluation. https://www.atlassian.com/try If you want to work with your company's Jira, you will have to ask your admins to get access.

Thanks for that explanation. Maybe it helps if I can tell myy colleagues and customers that others also take that effort to rename schemes to have an environment they can handle well. That way Versioning sounds good to me, I think I will try this out with my colleagues,

Hi @Nic Brough -Adaptavist-, thanks for this detailed answer. I also used naming it by using the project key, and have it often seen in our customers instances, but what I learned is, when new projects are created, often the teams using them want to have it working like an existing project. Renaming the schemes then is…

You can set the security level as post function and hide the field for editing, then it does not depend on the user and the user can not change it (even without hiding the user will not be able to change it, if the user is only assigned to one security level, because the user can choose only from that levels where the user…

Yes, thats right. Sorry, I have no idea then. 

Hi @Axel, if the Testuser can create issues in other projects, you should check the "Create Issue" permission in other projects. If the Testuser has permission to create an issue in an project, he can select it on the create issue screen even if he can not see that project. You can restrict the users, that can be assigned…

Ah, you are too fast, @Nic Brough -Adaptavist-

I think this should work using Issue Security. If you create a Scheme with two security levels, called Bug and Task and for each level, you add the users that should be able to see the Bugs or Task, and assign that scheme to your project, you can use this security levels to restrict the users. To have that working…

Hi @Shawn Danisa, I am sorry that I can not help you with the stacktrace, but why don't you just move the issues from one project to the other using the Move Issue function if both projects are in the same instance. You will not have to export and import then...

HI @Marzi Goodarzian, just to get it right. You want that one group of users can see only one issuetype and another group of users can see only another issue type?

If you are in your paid support period, you can just upgrade to the latest version. If you run out of maintenance, you need to renew your maintenance (for at least one year), then you can upgrade. Cost of maintenance depends on user tier and hosting (Server / Datacenter).

Hi @Akshay Laykar, and welcome to our community. It seems like you are using jira cloud, so maybe this add-on will help: https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions?hosting=cloud&tab=overview At least in documentation is described what you want to do:…

I never tried that Add-On before, so I have no experience I can share with you, but reviews look OK and there is at least some documentation, so maybe you can just try it in a test environment if available if it does what you expect.

Hi @Glenn Engelman, there is this KB article that describes how to do that, but you might loose some data within this process https://confluence.atlassian.com/jirakb/how-to-merge-two-different-jira-cloud-applications-together-779160767.html There are also the issues noted that may cause the problems.

Ok, you can do it without that, but that will mean a lot more work.... Find out, which stories are within each epic. Then use the following JQL "parent in (storyid1, storyid2,...)" to configure each epic as swimlane. But at least I won't do that, as you must add every story when it is created to you JQL queries to have a…

Hi @Eddy Dickens, you can change the default template when you go Email this issue configuration and then to Contexts. Choose there the context that applies to your project. There you have to option to choose another default-template (Content-Section > Template) If there is no template you want to use, you must create it…

You are right, sorry. There is no direct link from Sub-Task to Epic, so Jira is can not connect them both if the Story is not present. Maybe you can do that by using queries instead of epics as swimlanes, but that means a lot of work, because you will have to add the swimlane for every epic by hand. If you have the…

Technical Task will be the right one, as it looks that there is no Sub-Task named Sub-Task. You can use "issuetype in subtaskIssueTypes()" instead to have it working if there will be more Sub-Task-Types added in the future. The swimlanes can not be shown any more, because you filter out the epics. If you want to have the…

Hi Eric, do your subtasks appear on your board without that quick-filter? Do you use any swimlanes?

Hi, if it is just a GET - Call, you can just use the html-include macro (may it must be enabled https://confluence.atlassian.com/conf210/administrators-guide/installing-plugins-and-macros/enabling-and-configuring-macros/enabling-html-macros )and insert the URL of the API-Call in there.

This has been discussed also here, maybe there is some interesting information for you. https://community.atlassian.com/t5/Jira-discussions/What-archiving-strategies-do-you-have-for-Jira-Share-your-tips/td-p/788869

Hi @Regg Person, there may be reasons to have JS and JSD on different servers, for example if you want to make the customerportal available to the public (then JSD will be be too as it is connected) and JS should not be available. But if there are no such reasons, then it works perferctly fine to have them both on the same…

I am wondering if the , just after the value might be a problem, but I am not sure about that. Maybe you can try to tick the "Map field value" checkbox. Then the importer will show you the values found in the csv file and lets you choose, which issue type you want to map it to.

But you should do a backup of your data (hoemfolder/database) before upgrade to be safe if the upgrade fails in any way.

Hi @Stephanie Nobecourt, welcome to our community. Good to hear that your problem is already solved.