Tarun Sapra Community Champion

Hello @Vered Tsukerman What I suggested for you is the out of default out of the box approach. But there is a paid plugin available for this purpose. https://marketplace.atlassian.com/apps/1210818/scroll-versions-for-confluence?hosting=datacenter&tab=overview…

From the docs https://confluence.atlassian.com/doc/page-restrictions-139414.html

Hello @Vered Tsukerman You can use the "Page level permissions" so that only you and your colleague can view and edit the page and no-one else. And once your work is done then you can remove the restrictions so that everyone can view the page.

Glad to know @Jeetendra Dash that it helped, please upvote, accept answer so that others are helped as well.

Then you can try using the behaviour modeul of the SR plugin which works on create and edit screen. https://community.atlassian.com/t5/Answers-Developer-Questions/Behaviour-plugin-to-restrict-linkedissue-types/qaq-p/536508 def links = getFieldById("issuelinks") def linkissue = getFieldById("issuelinks-issues") def linktype…

Hello @gagan m s If the user is trying to link an issue to another issue via the create issue form then you can add a check in the validation phase of the create transition and easily avoid linking of the issue types of same type.

Because from the formatting it wasn't immediately clear is the sub-tasks have a "issue id" value or not.

From the docs * Referencing the unique "Issue Id" number of the regular issue in the "Parent Id" column. Do not include any value in the "Issue Id" fields for sub-tasks.

Hello @Conor Smalley Can you share a screenshot of the first 4 rows, as the data pastes in not clearly formatted. Ideally, each issue should have a unique issue ID and parent ID should be present only for sub-tasks and this parent ID should be same as the issue ID of the actual parent.

Duplicate https://community.atlassian.com/t5/Next-gen-questions/How-to-turn-on-voting-in-next-gen/qaq-p/962324

Hello @Juli Mane Currently it's not possible to do what you want, as it's an open ticket. https://jira.atlassian.com/browse/JRACLOUD-71075 As an admin, I'd like to place custom fields between the description and the comment section in the New Jira issue detail view

If your tempo version is earlier than 8.x then I am not sure how to do it, best is to reach out to tempo support.

https://tempoplugin.jira.com/wiki/spaces/TEMPO/pages/172785843/Reports

Hello @Lisa Jässl You can create a custom report in tempo, in that report you can feed the JQL filter of your wish and the group by "version"

Hello @[deleted] Based on your description, it's evident that you are using 2 separate Jira instances and linking issues belonging to those instances. Out of the box it's not possible to query about "remote linked issues" It's an open ticket https://jira.atlassian.com/browse/JRASERVER-28064 With a paid plugin it's possible…

The kind of requirement which you have is easier to implement using the backend API instead of behaviour.

Hello @[deleted] Instead of using Behaviour for this, why don't you implement this change in the post-function of the create transition of the sub-task.

Hello @Kumar Based on your requirement I suggest you to use the behaviour module of SR plugin which get's activated at the time of create issue screen popup https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html

Hello @Kumar In the "Additional Actions" section of the create sub-task post-function you can set the default description issue.description = 'default description'

assignee was EMPTY DURING (startOfDay(), startOfDay(-1)) and assignee is not empty This is what comes to my mind right now, in case the assignee was empty yesterday and today it has a value, may be someone from the community can come up with another solution. If I do "assignee was empty before startOfDay()" then it will…

Hello @Janine Daniels You can use "2 dimensional gadget" to plot issue types vs statuses

For the burndown chart you can easily switch the Burndown chart to "Issue count" instead of hours

Hello @Janine Daniels You can use the sprint report. https://confluence.atlassian.com/jirasoftwarecloud/sprint-report-777002722.html

I have done it multiple times with many plugins, but still I strongly suggest you to have a proper test instance in place so that you can play with all such scenarios. 

Hello @Niranjan "Uninstalling" the plugin never removes any data from the DB. Thus, when you install the plugin again then you should see plugin templates again.

Hello @turo If you take a backup of a single space from cloud then it should contain only 1 space and not 2. I am not sure if that's the case that it's containing 2 spaces. Are you sure that the server instance doesn't have a space with exact same "key" which you are trying to restore from the cloud instance.…

You can also write a post-function that populates a custom field with "Yes" or "No" based on whether the story has linked story with same version or not. And then later you can query in the issue navigator to get all issues with "yes" and all issues with "No"

Hello @Carl-Marcus Scheffler Personally, I find the underlying schema of Jira to be pretty complex. For your requirement I would just write a small groovy scripts that lists all the stories which are linked to other stories but they don't have the same fixVersion. You seem to already have script runner plugin installed,…

Hello @Helle Overbeck In your case one of the way I can think of is to write a custom listener. The custom listener will be triggered everytime there is a "Issue Move" event and if the issue is moved to an project of different category then relevant stakeholders can be informed by email about it and they can inform the…