Associating existing issue with a branch

outatime · February 27, 2018, 5:32pm

Hello,

When creating a new issue, I can associate it with one of existing branches or tags (top right corner, above Labels). I’m not able to do it after creating the issue — is it desired behavior?

Thanks!

Update: relevant (I guess) code:

github.com

go-gitea/gitea/blob/master/templates/repo/issue/branch_selector_field.tmpl#L3


{{if and (not .Issue.IsPull) (not .PageIsComparePull)}}
<input id="ref_selector" name="ref" type="hidden" value="{{.Issue.Ref}}">
<div class="ui {{if .ReadOnly}}disabled{{end}} floating filter select-branch dropdown" data-no-results="{{.i18n.Tr "repo.pulls.no_results"}}">
	<div class="ui basic small button">
		<span class="text branch-name">{{if .Issue.Ref}}{{.Issue.Ref}}{{else}}{{.i18n.Tr "repo.issues.no_ref"}}{{end}}</span>
		<i class="dropdown icon"></i>
	</div>
	<div class="menu">
		<div class="ui icon search input">
			<i class="filter icon"></i>
			<input name="search" placeholder="{{.i18n.Tr "repo.filter_branch_and_tag"}}...">
		</div>
		<div class="header">

github.com

go-gitea/gitea/blob/master/routers/repo/issue.go#L756


			} else {
				ctx.Data["MergeStyle"] = ""
			}
		}
		ctx.Data["IsPullBranchDeletable"] = canDelete && pull.HeadRepo != nil && git.IsBranchExist(pull.HeadRepo.RepoPath(), pull.HeadBranch)
	}


	ctx.Data["Participants"] = participants
	ctx.Data["NumParticipants"] = len(participants)
	ctx.Data["Issue"] = issue
	ctx.Data["ReadOnly"] = true
	ctx.Data["IsIssueOwner"] = ctx.Repo.IsWriter() || (ctx.IsSigned && issue.IsPoster(ctx.User.ID))
	ctx.Data["SignInLink"] = setting.AppSubURL + "/user/login?redirect_to=" + ctx.Data["Link"].(string)
	ctx.HTML(200, tplIssueView)
}


// GetActionIssue will return the issue which is used in the context.
func GetActionIssue(ctx *context.Context) *models.Issue {
	issue, err := models.GetIssueByIndex(ctx.Repo.Repository.ID, ctx.ParamsInt64(":index"))
	if err != nil {
		ctx.NotFoundOrServerError("GetIssueByIndex", models.IsErrIssueNotExist, err)

howl · February 27, 2018, 6:45pm

Straight from the horse’s mouth:

Searching, filtering and editing is not yet implemented, so the branch can only specified when creating the issue

You’re very welcome to submit a pr or issue if you have the time

outatime · February 27, 2018, 8:13pm

Just a git blame away… Sorry for not digging deeper

/solved

howl · March 3, 2018, 11:31am

Issue created