Ravi Sagar _Sparxsys_ Expert

Hi @Aishwarya Singh Trying using the REST API. This will give you the list of resolved comments. CONFLUENCE-URL/rest/api/content/12345/child/comment?&expand=extensions.resolution&location=resolved Also refer to the Confluence API Documentation. From the UI if you go to page's more details (3 dots on top right) there is an…

It seems like connection issue instead of TLS though.

Hi @IMTIAZ SHAIK Is TLS checkbox checked or unchecked? Ravi

Exactly. I always add a label or update a field to uniquely identify bulk imported issues. Combining it with Date range it is much easier to delete them or do something with them if needed.

Hi @Aashish Gupta You cannot hide summary field (unless it is possible in the latest version which is unlikely), it is a mandatory system field. What you can potentially do (with some hacks) is hide it and populate it with some text. You can trying some JavaScript. You will get some pointers here. Ravi

Hi @Paul Male On cloud you don't need to worry about that. Ravi

Do you need to do this for parent and subtask both? Do you have same workflow for both of them?

Hi @Frank Vasconcelos What have you done to allow the users to view issues? Ravi

Hi @James BonTempo You need to look into the Issue History. It is not available in the Issue Navigator. There are some paid add-ons that can export this history into a table as well but not out of the box. Ravi

Hi @Jarrod Thomas I am not sure if I understand your question. Are you trying to create a custom Issue Type in Jira? If yes then it is possible and you can add your own custom fields. Ravi

Hi @Andre Giuseppin You would need an add-on for that. Take a look at Extension for Jira Service Desk. Ravi

Now it is clear. In that case use a post function to update the "Original Due Date" custom field not a scripted field. What you are doing is baselining. Also take a look at some apps like BigPicture or Portfolio, these have such features built in but for the time being post function should do the job.

Hi @Martin Try this. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.user.ApplicationUser def customFieldManager = ComponentAccessor.getCustomFieldManager() def cField = customFieldManager.getCustomFieldObjectsByName("User Picker Field") def cFieldValue = issue.getCustomFieldValue(cField[0])…

Hi @sakthivel-systech Most likely you would not loose your data (if done properly). Since you are using Jira 6.1 you will have to do couple of jumps. Most likely 6.1 > 7.0.11 > 7.13 > 8.4. I know 3 jumps but that's why it is recommended to upgrade before end of life. Anyways before upgrade take a look at your add-ons,…

Hi @Rob Horan Have a look at Multi-Level Cascading Select. Jira natively can't have 3 level (only 2 are supported). I hope it helps. Ravi

Hi @Aisha M Yes that is the job of the scripted field, it will have the due date. What do you mean by "..value entered first is fixed"? I should have asked, why are you doing this? What is your objective? Ravi

Hi, You need to use Send a custom email which is a Script Post-Function. There is a similar example here. In the example instead of watchers just fetch the linked issue assignee. Ravi

Hi @[deleted] Jira Software is another application on top of Jira Core. So you always have Jira Core if you have license of Jira Software. Ravi

In the new scripted field write this code. issue.dueDate May be 2 more configurations if you are dealing with date field. Searcher: Date Time Range picker Template: Date Time You may need to add more code to handle errors. It is bare minimum. Ravi

Hi @Nictiz BITS It is because of the view of the Issue Navigator which is set to Detail view, change it to List view and the url would go back to the original. If you are sharing this url with user it has no impact on the functionality. The result will also show the correct issues. Ravi

Hi @Sreenivasan D Look at the Edit Issues permissions in your permission schemes. Everyone else can just have Browse projects permission. Ravi

Hi @jrii Project administrators can manage versions, components and manage people in the roles. They need not to be Jira administrators. Ravi

Hi @Jawahar Sinha Few ways of doing it. To keep it generic you can rely on Issue Update event which will be triggered on all updates and in the email template you can see the field change. For capturing the security level change only. Put the field on a transition screen only (not on create/edit screen) and show this…

Hi @nandhini_chandrasekar 1 and 2: Make sure the "Linked Issue" field is present on the create issue screen, check the "Issue Type Screen Scheme" and "Link Issues" permission is given to other users' roles who wants to create a link, it will be done in the "Permission Scheme" used in your project. 3. Most likely the board…

Hi Siva, Are those your own filters or created by someone else. Most likely they are not shared. Ravi

Hi @Jason I believe there is a feature request already for this (anonymising names/emails from the portal and notifications): https://jira.atlassian.com/browse/JSDCLOUD-3308 and https://jira.atlassian.com/browse/JSDCLOUD-2381 You may want to vote for it. Ravi

Hi @Chakravarthy_R Jira won't stop you from doing that. You will have to rely on a workflow validator or some scripts (behaviours). You would need an additional add-on to do that. In case you have ScriptRunner installed it is not very difficult to achieve. Take a look here. You can do both ways - update parent due date as…

Hi @Raghavendra Amara For Jira 7.5 take a look here. It has the details. Also keep in mind that eventually you might be upgrading Jira as well. This page will list the platform requirements for each version. As always test on staging instance first. I hope it helps. Ravi

@Clarissa V Let me try to help using these points. * Permissions are either global or project based * Project specific permissions are defined by permissions schemes in Jira. These schemes can be shared, that means two or more projects can have same set of permission. * Permission schemes have a list of permissions along…

So your project is FSDS and you have only 1 screen scheme mapped to all the issues. When you click on "Flexys Default Screen" do you see the fields that you added? If yes then - The field is available in your project but it might be possible that the custom field either is hidden or has a context set which is not allowing…