Population of the language and host based on the host you are on and the language of the contentlet when adding relationship

Open
#26,484 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
frontend

Research direction

No file, test, or code entry point is named. Start by reproducing the relationship-creation flow described in the issue and inspect where the language and host fields are populated; done means both fields default to the contentlet's language and host every time a relationship is added.

Written by the indexing model from the issue text.

Description

OKR : Customer Support Priority : 4 Low Team : Maintenance Type : New Functionality
Parent Issue

No response

User Story

The population of the language and host is based on the host you are on and the language of the contentlet when adding a relationship.

It would add a value to add language and host by default based on the language and host of the contentlet while adding a relation.

According to the current implementation, while adding a relationship

  1. Language populates for the first time while trying to relate the content.
  2. The next time we try to relate, the language field is empty and not populated by default.
  3. Also, populating the host by default would add value.
Screenshot 2023-10-20 at 12 38 49 PM Screenshot 2023-10-20 at 12 39 06 PM
Acceptance Criteria

Populate language and host by default while relating content every time depending on the host and language of the contentlet

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.zendesk.com/agent/tickets/113834

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotCMS/core

All issues in dotCMS/core

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.